>  > ZSI explicitely avoids coupling to any transport mechanism. We
>  > currently look into using ZSI instead of SOAP.py, for that reason and
>  > because it's DOCUMENTED (surprise! ;).
>  
>  That's fair but I'm trying to document it for people who would not want
>  to be in the business of rolling their own transport...

I think you missed the point.  ZSI was designed to work with
*pre-existing* transports, such as Apache (such as through mod_python
which is what we do), Python's HTTPServer (the release includes the
server I use for SOAP interop testing), or sys.stdin, sys.stdout (which
the docs show). Any object with a read method can be used for input, and
anything with a write method can be used for output.

Hope that's more clear.

>  jsut want to point their server at their class and have it do all CGI
>  wrapping for them. SOAP::Lite and the PHP equivalent have this feature.

I know I can do at least as well as Paul K. :)  (Just kidding; he's been
very helpful in the interop testing.)  Please take a look at the ZSI
doc; if it doesn't do what you want, I'm probably quite willing to add
what's missing.

ZSI is at http://www.zolera.com/resources/opensrc, including PDF and
HTML doc separate from the kit.  I'll be release ZSI 1.1 in a day or
two.
	/r$

-- 
Zolera Systems, Securing web services (XML, SOAP, Signatures,
Encryption)
http://www.zolera.com

_______________________________________________
XML-SIG maillist  -  XML-SIG@[...].org
http://mail.python.org/mailman/listinfo/xml-sig