Re: Question on Client - Server communication

[Caffeine Junky <nospam@hotmail.com>]

On Fri, 05 Jul 2002 04:08:18 -0400, Preben Randhol wrote:

> I'm doing a small program to learn a bit about socket programming with
> clients and servers. Besides I need the program.
> 
> What I want is an application that can talk to the same application
> running on a different machine. This is ok and no problem. However I
> cannot know the port the application is listening to (there may be
> several users runnig the same application on the same machine).
> Therefore in order to contact the other application I need a server
> running on each machine with a known port number. Then I can do this (_A
> = on machine A, _B on machine B): App_A contacts Server_B which tells
> App_B to contact App_A on port XXXX. So Server_B will only deliver this
> message to App_B and not the whole stream between the two. Does this
> seem like a OK way to do this? Or is there a better way using socket
> programming (not GLADE).

Use port "forwarding". Very simple.

The server designates a standard port. The application connects to the
server on that port. The server then tells the application to switch to
port number X and opens a connection on that port. This leaves the
original port open to recieve more app requests. There are alot of
servers that do this. Check out thier source code.

Apache comes to mind.


St4pL3