Mike, and everyone, I am curious what folks in the community are doing with SOAP or XML-RPC in general, and specifically with AOLserver. And with respect to AOLserver, how have you implemented SOAP functionality. Me, I'm just playing with it at this point with AOLserver. I've implemented Dave Bauer's/Aaron Swartz's XML-RPC module (built on top of ns_xml), and on top of that built an XML-RPC protocol that implements a remote site search. I've found it works, works well in fact, but it sure seems sluggish (XML-RPC calls from my machine to my machine in the order of several tenths of a second, where I bet that the classic POST and parse mechanism would have been on the order of hundredths of a second. I'll tell you one area where .NET just kicks butt over what is available today (that I know about) in terms of SOAP/XML-RPC. .NET comes with a utility (wsdl) that visits a wsdl compliant SOAP/XML-RPC site and then creates for you a .NET compatible proxy class that performs all the SOAP/XML-RPC calls for you. You use normal local calls to get/set the local proxy class and the SOAP/XML-RPC magic happens for you in the background. Very slick, and a very slick way to get a client working in a matter of minutes. Oh, man, every day I spent past that first day on my remote search demo sure felt like wasted time after seeing a demonstration of the .NET wsdl utility that did what took days for me in the time it takes for you to type wsdl <url> <return> What are you folks doing, (are any of you getting paid for this), and what do you feel is needed for AOLserver to become a reasonable/popular platform for these sorts of applications? Jerry ===================================================== Jerry Asher [EMAIL PROTECTED] 1678 Shattuck Avenue Suite 161 Tel: (510) 549-2980 Berkeley, CA 94709 Fax: (877) 311-8688
