| problem is in the Execute command section's Do Until loop. | It's probably | blocking, slowing everything down including xmail's response to the | ctrlclnt.
Yes, because ASP technology is not designed to run external processes lasting extended amout of times. And therefore doesn't contains commands such as "DoEvents" known from VB/VBA etc. Moreover, some users reported that the ctrlclnt.exe incorrectly report its state and doesn't notify the calling process that it's finished, although I never experienced this behaviour and the current WAI solution is working fine for few hundered users on my server. The only systematic solution is to use COM (or COM+) component. AFAIK there is only one available, the eyeXMail, but it's very unstable and buggy (or at least was at the time I abandoned it), so this is smaller evil. Unfortunatelly, I can't write such component, because I'm writing in Visual Basic and it's variations (VBScript, VBA, VB.NET etc.) and this language is NOT intended for writing COM components. If someone want to help here (by writing relatively simple component implementing the XMail's CTRL protocol) and knows some language like C++ or Delphi, I would be very happy to use this component. If someone wants to do that, I can send my idea of what the interface should be to seamlessly integrate into WAI and also allow use to other applications. The other way is to modify XMail configuration files directly, but this is in most of cases impossible due to the internal indexing, which makes modification of files at runtime almost impossible. The other way is to use as configuration repository some standard repository handling changes at runtime, for example XML files or SQL database. The XMails CTRL protocol is generally not good for web applications, as any network communication protocol, because it cannot guarantee realtime responses. Better solution may be for example COM component directly communicating with XMail). All the solutions specified in previous paragraph requires serious changes in XMail, probably platform-specific and cannot be reasonably expected to be implemented in near future. Ony good and functioning idea I have is to store all commands to XMail in some queue and execute them asynchronously, independently on the web application. To have cached lists of users etc. and so on, like it's in handling of frozen messages by WAI. But this solution would lead to more complicated setup of WAI and when there are users who don't know how to use task scheduler or create virtual web directory (not meaning correct writing of the config.xml file), I think so more complicated setup would kill them. And mainly, this would mean to rapid rewrite of WAI itself, what is definitelly out of my current time posibilities. I have developed the architecture, but no time to code it. -- Michal A. Valasek Altair Software Production __________________________________________________________ Censorship can't eliminate evil; it can only kill freedom. E-mail: [EMAIL PROTECTED] * ICQ: 6160893 * GSM: +420-603-828493 For list of all my web projects visit http:[EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
