> And second question, more global: Isn't it worth to add good and native > timeout functionality to TWSocket so that thousands of developers > hadn't invent a bicycle again and again? I know about TIcsTimer > and so on, but it is not 'out of the box'.
This is underway. but designing a general purpose timeout is not so simple because you potentially have thousands of components (server side). You can't create a TTimer for each one or you'll run out Windows resources very quickly (bad scalability). Currently you should implement a timeout yourself. Using a single TTimer and carefully crafted code will do the job. Basically you need a list of all your timeout \"jobs\" and have the timer event scan the list a do whatever appropriate is to evaluation and handle the timeout. -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
