Hello Albert, You only need a threaded approach if you have to run very long code, meaning if your code (for example to parse incoming data, or to get data that need to be sent or so) is long (so blocking).
when you write code in non threading design, the time your code is executing nothing else will happen, meaning no data is sent or received. it only will happen when your code end, that is when your application enters the message pump. hope this is somewhat clear. --- Rgds, Wilfried [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html http://www.mestdagh.biz Monday, November 26, 2007, 15:19, A Drent wrote: > Until now I alway build our applications using 'normal' sockets. Currently > I've got an application server build which is running well for years now. > Now I've modified the server so it is able to process soap messages. The > soap messages are send by the webserver to the application server on another > engine, parsed and executed and result is sent back. So far so good. But I > wonder, when do I have to use a threaded approach. 'Long' and 'blocking' as > said in the ics sample is very vague for me. I ask this because of a > possible near redesign of the server. > Albert Drent > University of Groningen -- 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