> Take a look at http://xml.apache.org/guidelines.html, in > particular the > source repositories link has instructions for creating patches. > > It's probably best to just post it on a website somewhere if > you have a > place. If not send it to me privately and I can post it if > necessary. For > small patches it's ok to send them to the list, 70k seems > rather large. >
All right; didn't know there was a diff command in CVS; pretty useful :) I made the diff available at: http://lambiek.amplexor.be/downloads/xindice-utf8-patches > > All the corba stuff is in that directory. I wouldn't worry > too much about > it though, as we're going to remove CORBA in the next > revision after 1.0. > That is when you're patches would make it in too since they > break existing > data files. I'd really appreciate your help on making sure we > properly > handle these issues in the replacement API. It will most > likely be XML-RPC, > but may be SOAP. We'll actually do both, but XML-RPC is > probably more > likely for the primary API. > 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)? * 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? * 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? James
