Re: [twsocket] Sever architecture

2006-08-18 Thread Wilfried Mestdagh
to:[EMAIL PROTECTED] On > Behalf Of Francois Piette > Sent: Thursday, August 17, 2006 11:46 PM > To: ICS support mailing > Subject: Re: [twsocket] Sever architecture >> Imagine a server with many concurrent connections but that only allows >> one connection at a time

Re: [twsocket] Sever architecture

2006-08-18 Thread Angus Robertson - Magenta Systems Ltd
> Would a TTimer OnTimer event in the main application thread mess > with the message pump? The timer is driven by the message pump and is quite safe, if not essential in most ICS applications to handle timeouts, lockouts, etc. Angus -- To unsubscribe or change your settings for TWSocket mail

Re: [twsocket] Sever architecture

2006-08-18 Thread Brian Sheeres
n the main application thread mess with the message pump? Thanks!! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Francois Piette Sent: Thursday, August 17, 2006 11:46 PM To: ICS support mailing Subject: Re: [twsocket] Sever architecture > Imagine a ser

Re: [twsocket] Sever architecture

2006-08-17 Thread Francois Piette
> Imagine a server with many concurrent connections but that only allows one > connection at a time to submit a request, access/manipulate data and then > send the results back to all other connections. In other words all requests > (regardless of which connection it's coming from) must be serializ

[twsocket] Sever architecture

2006-08-17 Thread Brian Sheeres
This is less of a socket question and more of an implementation question. Imagine a server with many concurrent connections but that only allows one connection at a time to submit a request, access/manipulate data and then send the results back to all other connections. In other words all requests