Hello Angus, You are true, I made a mistake talking about "multiple threads", I meant multiple components in a single thread with a thread dedicated to the smtp component's so it is separated from the main GUI thread so the visual interface (if any) should be always responsive whenever the smtp thread is working hard.
regards. >> The application I'm working on is 9 years old, has many thousands >> of man hours spent on it, and whilst it would be nice to have a >> single TSmtpCli, in order to avoid a massive code rewrite it's much >> easier for me to have lots of TSnmpCli components, rather than one >> (you can't see it, but I can of course). ARMSL> The issue we were discussing was not the use of a single TSmtpCli which ARMSL> is clearly unsuitable for all but the most simple mail servers, but ARMSL> whether you should be using threads with multiple TSmtpCli components (or ARMSL> most other ICS components for that matter). ARMSL> I have an application that captures data on 400 TWSockets simultaneously, ARMSL> in a single thread. ARMSL> As was said, two or more threads are beneficial where there are multiple ARMSL> processors available to the application and you can hog the entire server, ARMSL> or where you really are handling thousands of simultaneous connections. ARMSL> Angus ARMSL> -- ARMSL> To unsubscribe or change your settings for TWSocket mailing list ARMSL> please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket ARMSL> 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
