I'm writing a proxy type of application for irc and I noticed an issue twice
last night that had me puzzled. I have 1 wsocketserver component on my form
and I spawn a wsocket client for the remote connection since this is a local
proxy. When inbound remote connection data comes in i write the packet data
to a Tmemorystream, assemble the data and then fire an event which i then
use wsocketserver to send the data over loopback. Everything worked fine
until last night when i ran it for a few hours. It seems that i stopped
getting updated text in irc and when i opened a packet sniffer my program
wasn't sending packets over loopback at all. The socket state was still
connected and no errors or exceptions were thrown so it wasn't anything that
i had done to create an external issue. About 60-90 seconds later the data
appeared on my chat screen and there was quite a bit of it. It seems like
the wsocketserver queued and buffered the data for nearly a minute and a
half before sending the packets, any ideas on how i can avoid this or maybe
how this happened? Most of the wSocketServer properties are default, along
with the client and both are not threaded. Only 1 client connection is
connected always so that wasn't the issue either, the only thing i think it
could be is i had the send flags set to wsSendUrgent instead of SendNormal.
LingerOnOff was set to LingerOn, would that affect it maybe? Anyhow i'm lost
so i'd appreciate any advice on how to ensure that data is pushed out as
soon as I call a send operation rather than have the data build up for some
time and then send.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
