Do it all in the same thread and use post message to send the strings to the thread and put them in a queue and then when the socket is not reading send the strings in the queue. On Oct 18, 2014 5:01 AM, "Krzysztof" <dib...@wp.pl> wrote:
> Hi, > > I need to use TTCPBlockSocket on client side. I need to listen for > server messages so I moved TTCPBlockSocket.RecvString(100) to another > thread loop. The problem is that I also need same socket to send > messages from main thread. I suppose that I need to use critical > sections to avoid deadlocks. I'm worrying about efficient because > TTCPBlockSocket.RecvString(100) routine need to be also between > critical section access (100 milliseconds sleep). Is exists any other > way to do this? Maybe better use TApplication.OnIdle event and call > RecvString there? > > Regards > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > synalist-public mailing list > synalist-public@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/synalist-public >
------------------------------------------------------------------------------
_______________________________________________ synalist-public mailing list synalist-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synalist-public
