Michal, I already wrote ActiveX component to substitute CTRLCLNT in your WAI. I wrote it in Visual Basic. ASP works with it a lot better than with shell executables.
The problem that discussed here I noticed immediately when I installed WAI. I didn't measured any CPU time, but I just didn't like the idea of executing a program from ASP. Besides, WAI is noticeable slow in some operations. Before spending my time for writing new component, I looked at eyeXMail. And I agree, it's not good idea of hardcoding CTRL commands inside of a component. For that reason I didn't choose it and decided to write my own. Despite the fact that I used Visual Basic instead of C++ (because I don't know C that well), it is working a lot faster that shell from ASP. Anyway, what do you think about ActiveX component? I'm sure you too can write it in VB. I know, if Shawn will take care of that component, then it would be great, but I was just wondering what do you think about ActiveX written in VB. Thanks, Lev Shamilov <[EMAIL PROTECTED]> On Wed, 3 Jul 2002 14:29:45 +0200 "Michal Altair Valasek" <[EMAIL PROTECTED]> wrote: > > Hi, > > I thought you stopped work on eyeXMail. If you have time and energy to > work, here is my suggestion how the ideal component for XMail CTRL > protocol should work. > > At first, it should implement only general framework for communication > of XMail. Therefore it would be not restricted to specially implemented > things, such as methods to create user, to delete user etc. Therefore, > the component must not be updated every time the new CTRL command would > be added. > > My idea is that I'll have component with the following interface. I'm > using the symbolic VB syntax (I jumped from the assembler and > hexadecimal instruction codes right to Visual Bassic, happily skipped > all the things like C etc.). > > ServerAddress, ServerPort, ServerUser, ServerPassword -- properties, > identification and authentication for Xmail > > AFAIK you can get XMail version from CTRL, then this should be > accessible too trough some method, for example GetServerVersion. > > Method CtrlExec (ByVal CommandName As String, Optional ByVal > Parameters() As String, Optional ByVal PostData As String, Optional > ByVal SortIndex As Integer) > > CommandName - the XMail command name, ie. "userlist". > Parameters - if present, then it's array of string containing command > parameters. > PostData - if present, then it's content of command, as used for example > by "cfgfileget". > SortIndex - if present, then output is sorted by column specified with > index beginning at 0; if not present, the output is not sorted. This > function is here because it's much quicker to do sorting in compiled > code than with some interpreted script. > > Returned is array (or collection or some other similar structure), where > every item contains one result row, in form of another aray containing > the line items. So 3rd item on 2nd line would be Result(3)(2). OR you > can supply simple two-dimensional array. > > Method CtrlExec2 has the same parameters(except for SortIndex), but > returns raw unparsed string data exactly as given by XMail. > > All errors should be raised as standard exceptions, which can be easily > catched in any programming language. > > - - - 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]
