's nothing to do with the data, but
I can't get it to fail even when test client is run remotely using
(via NAT).
On 09/11/06, Fastream Technologies <[EMAIL PROTECTED]> wrote:
>
> Seems like a firewall problem to me.
>
> On 11/9/06, Arno Garrels < [EMAIL PROTECTED]>
I've written a fairly simple server app using the TWSocket component.
The app listens on port 80 for packets with a particular structure, and
sends a reply. I've tested it with up to 12 clients connected, all sending
requests as fast as possible, and all works well.
As soon as I connect a real c
I've written a fairly simple server app using the TWSocket component.
The app listens on port 80 for packets with a particular structure, and
sends a reply. I've tested it with up to 12 clients connected, all sending
requests as fast as possible, and all works well.
As soon as I connect a real c
