On Wed, 3 Jul 2002, Michal Altair Valasek wrote:
> > | 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. By using the code inside CTRLClient.cpp it should not be a problem to do that. > 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. I would say with a pretty high level of confidence even in a far future ;) Accessing files directly is Bad(tm) and a command issued to the CTRL server is lightning fast when used with CtrlClnt directly. As an example of the most "slow" command, a "frozlist" takes 0.5 sec average after the first run ( buffer cache warmed ). Commands like adding a user/domain takes 0.0-lots-of-zero-1 secs average. The problem is the freakin' ASP instead. Again looking at the code in CTRLClient.cpp it should not be a problem to build a DLL that does the job *sanely* Can the freakin' ASP load DLLs ? - Davide - 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]
