kee.nethery at elloco.com
Sun Apr 5 14:55:48 EDT 2020
Here’s how this should work.
Server has an IP and port number that it listens on. Client sends a packet from the same IP and some random port.
Computer routes the packet and it doesn’t have to send the packet out on the net. It goes out the client port and back in to the server port.
Server replies from its port to the client port (client is waiting for a reply).
Try talking to your server with a browser on your computer and see what the server response looks like.
> On Apr 5, 2020, at 11:22 AM, Bob Sneidar via use-livecode <use-livecode at lists.runrev.com> wrote:
> Hi all.
> I am creating a client/server socket based app and I am trying to develop both the client and server on the same workstation, and I am having difficulty. I *think* the issue is that the client and server cannot both be on the same system, but I’m not entirely sure. I’m asking the system to listen and also talk on the same port.
> Anyone have any insight into this?
> Bob S
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode