🚀 go-pugleaf

"roger" <rogersmail@ntlworld.com> wrote in message
news:423b0576$1@newsgroups.borland.com...

> So what your saying then is when i tell the server to open on
> port say 10245 i dont have to specify ie: My Internet IP, or
> 0.0.0.0 or my Router assigned IP, as long as his remote client
> makes a call to http://myinternetIP:MyPort then the server will
> detect it..even if i am not using a router...and even if my internet
> ip is say 62.63.64.65 and the server opens on 0.0.0.0..

The remote client can only connect to the public IP address, whether that be
a router or the listening server directly.  It has no concept of routers,
nor does it need to.

The listening server can only listen on its local machine, regardless of
whether a router is being used.  It has no concept of routers, nor does it
need to.

If you do have a router involved, then you need to configure it properly.
There is no getting around that.  As long as the router is configured
properly, then all incoming data from the remote client will be directed to
the listening server, and the listening server will think that the remote
client is connecting to it directly.  You do not need to add extra code to
handle that.  Everything you do with direct client->server connections still
applies even when a router is involved.  A router is just a piece of
hardware that is completely transparent to software.


Gambit