I'm sorry John, Let me try to clarify my point:
The people who are complaining are complaining because OpenSRS doesn't do "x" where "x" is their favorite thing. Much of the time the premise seems to be "well, I can't do the current API on my platform" -- and the available implementations (in PHP and as an Active-X component) seem to suggest otherwise. The code examples of whhat people want looked like ASP, which is Microsoft-centric even if the underlying code is not. I'll grant that the sentence you quoted may be in error, but it isn't particularly relevant to my point. I'll admit that I may be wrong because frankly, it doesn't matter. The important point is this one: "The nice thing about standards is that there are so many to choose from." The ClosedSRS component I mentioned elsewhere on this thread implements the socket communications and encryption. It will generate the XML or not. I think he has examples calling his component straight from ASP. -- Lynn On Mon, 27 Oct 2003 13:15:44 -0500, [EMAIL PROTECTED] wrote: >>>�it now seems to all be SOAP, XML, .NET, whatever -- but very >�Microsoft. > >�SOAP and XML are anything but MS centric, being standards much like SMTP >�and HTTP > > >�.NET is an application framework that runs on MS platforms ( and maybe >�UNIX/Linux at some point). You can program in any supported language, >�including PERL. > >�An XML WEB Service (usually implemented as SOAP over HTTP) would be both >�platform and language independent, the best of all worlds. > >�John Roche >�einfosystems.net >�Microsoft Certified Partner > > >�This mail was content checked for malicious code and viruses by >�GFI MailSecurity. GFI MailSecurity provides email content checking, >�exploit detection and anti-virus for Exchange &�SMTP servers. Email >[EMAIL PROTECTED] for more information.
