I need to add: if you want to use the advantage of multiple CPUs/cores,
single thread cannot do that.

On Tue, Jul 15, 2008 at 7:55 PM, Arno Garrels <[EMAIL PROTECTED]> wrote:

> Stratus wrote:
> > Thank you for your answer Fran├žois.
> >
> > Ok. Another question rises : As I have to save to disk every stream
> > received, should I process it on a different 'save to disk' thread,
> > or the internal TSocket buffers can cope the wait?
>
> I'm pretty sure that you do not need multiple threads for this purpose.
> Asynchron winsock API makes it possible.
>
> --
> Arno Garrels [TeamICS]
> http://www.overbyte.be/eng/overbyte/teamics.html
>
>
> >
> > Thank you.
> >
> >
> >> Basically, this is the way to go. Don't worry too much about 50
> >> components because the code is shared by all components. Only the
> >> data part is allocated for each. And you can use the same event
> >> handlers for all of your 50 components, provided you correctly make
> >> use of the "sender" argument in each event handler. Sender always
> >> refer to the component triggering the event.
> --
> 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
>
-- 
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

Reply via email to