>OK, of course I'd want to help. A few questions though: >* Have you started on this SOAP or XML-RPC API? Any ideas/discussions about > requirements? Or could/should I start looking at that myself (I had intended > to start learning SOAP anyway)?
Unless I'm overlooking something, I think SOAP is a little overkill for Xindice since the data returned will most likely always be XML and not a datatyped response. What do you guys think? >* If/when we switch to SOAP/XML-RPC, will the internal HTTP server still be > necessary? Or would whatever toolkit is used to make the SOAP/XML-RPC stuff > include a web server? If not, couldn't we do something with servlets or > webdav, in stead of maintaining our own HTTP server? Apache XML-RPC does have a web server class that could probably handle some of the other concerns about using HTTP as the transport: 1. ability to deny requests based on remote IP 2. SSL support SSL is going to be required when security is implemented , otherwise db usernames and passwords would be sent in plain text. >* Whatever the future, what functions exactly does the HTTP server fulfill TODAY? I understand it is used by the >CORBA connections, but does it server >any other purpose? The two server "plugins" both use the HTTP server. (HTTP Doc retrieval and the XML-RPC plugin). Speaking of the XML-RPC plugin, I apologize for not having a download available. I will have some CVS updates and hopefully a download later today: http://sourceforge.net/projects/xindice-xmlrpc/ Kurt _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
