Re: simple TCP/IP messaging

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Ook (usenet_at_nospam.emberts.com)
Date: 07/23/04 

Date: Fri, 23 Jul 2004 10:45:32 -0700

I'll post some samples tonight. One is a working chat client/server that
while not simple, does a good job of demonstrating exactly how you talk back
and forth with tcp/ip. I wrote a remote time generator in VFP based on this
architecture that allows clients to connect to a server app to get the
current date/time. It allowed for virtually unlimited concurrent
connections, managed time outs, etc. The hardest concept to grasp is that
for each incoming connection, you have to instantiate a new instance of the
winsock control to handle the communications with each individual client,
but you can create a hundred instances with no appreciable resource load.
There is a simpler dedicated sample that lets two instances talk to each
other - much simpler, but doesn't support multiple connections.

"Jeff Grippe" <jgrippe@hilldun.com> wrote in message
news:10g2ca8b1vk9616@news.supernews.com...
> Any help would be appreciated. Thanks.
>
> "Ook" <usenet@nospam.emberts.com> wrote in message
> news:eDW34qMcEHA.2352@TK2MSFTNGP09.phx.gbl...
> > It's not that simple. I've built apps that do this, and it takes a bit
> more
> > to get them to work. I use the MSWinsock control, and while the end
result
> > works very ver well, the biggest problem with this control is absolutely
> > pathetic documentation. I have some samples, but can't get to them until
> > later tonight.
> >
> >
> >
> > "Jeff Grippe" <jgrippe@hilldun.com> wrote in message
> > news:10g2autsfj8g0ee@news.supernews.com...
> > > Hello, Thanks in advance for the help.
> > >
> > > Does anyone know of an easy to use TCP/IP messaging library. I would
> like
> > to
> > > have something like the following:
> > >
> > > Receiving / Server App (meta code)
> > > Listen for TCP/IP messages && this is a DO WHILE .T. I would
imagine
> > > When Message Received
> > > Process Data
> > > EndWhen Message Received
> > > EndListen for TCP/IP messages
> > >
> > > Sending / Client App
> > > lcData = "Whatever I might need to send to the server"
> > > lcTCP = "192.168.0.200"
> > > SendTCPIPMessage(lcTCP, lcData)
> > >
> > > For my application I only need communication from the Sending App to
the
> > > Receiving App.
> > >
> > > Thanks,
> > >
> > > Jeff
> > >
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: Singleton SqlConnection object
    ... >> 2 certainly applies when connecting to a shared database server. ... >> That's plain client/server with its inherent scalability problems ... connections to a DB is a traditional Client/Server app. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: allowing incoming connections on any port (possibly dumb question)
    ... You need to have some thing "listening" on the port you are connecting to. ... To get a better understanding of socket programming on .NET, ... > How do I allow incoming connections to my machine? ... > I'm writing a little client/server app, and am planning ...
    (microsoft.public.win32.programmer.networks)
  • Re: Computers joining customers domain - how to best configure
    ... At this stage I think I'm talking about allowing control of the local ... I have a client/server product that is sold to a number of customers. ... The server runs Windows 2003 Std and is in it's own workgroup. ... and are in the same workgroup and have the same local user accounts. ...
    (microsoft.public.windows.server.general)
  • Access on VPN -- seeking solutions
    ... offices around the country with multi-user permissions set to control ... I've also heard web development might be easier with SQL ... I've heard there may be ways to go the client/server route that would ... avoid the speed issues with VPN, ...
    (comp.databases.ms-access)