I had an idea for a much slimmed down protocol called XRPC, I don't know if anyone would like to work on an implementation with me, but it's a much leaner, and attempts to support things like literal XML and a tighter binding with XML Schema datatypes. Also supports an asynchronous model.
blog entry at http://tbradford.blogspot.com/2003_09_23_tbradford_archive.html spec and schema are at http://tbradford.blogspot.com/2003_09_26_tbradford_archive.html
Ryan, XMLWriter needs to be modified to support proper UTF-8 serialization... I took a shit-fit this weekend and created my own derivation of Apache XML-RPC's client to do all this stuff, you might want to take a look at it:
http://tbradford.blogspot.com/ 2003_11_30_tbradford_archive.html#107023953359946198
-- Tom Bradford - http://www.tbradford.org/ CTO - The dbXML Group - http://www.dbxml.com/ Project Labrador - http://www.dbxml.com/labrador/
On Dec 3, 2003, at 4:54 PM, Ryan Hoegg wrote:
Vadim Gritsenko wrote:
Not yet. I am out of free time right now (it's hard to find time for two jobs, three projects, and family, so there is still some time left to sleep), but I'm thinking I'll catch up on xindice in the beginning of next year (february timeframe). Then, next beta release, or 1.1 release, is in order (depending on issues left). Xindice also will be shipped in the Cocoon, in embedded mode, and some samples will be provided.
BTW, how's your work on chaning XML-RPC protocol so it does support all the necessary return datatypes?
Vadim
I for one have found success using Xindice 1.1. It has served me well as a hierarchical persistent store for one of my projects, and I am eyeing it for use in several others. I also happen to be a committer on Apache XML-RPC. So, I'll raise my hand and ask what I can do to help. Got an archive link for me? I have not been subscribed to xindice-dev for many months yet, so I may have missed it.
Re: changing the XML-RPC protocol, I have been down this road once and Dave Winer is not at all open to changes to the protocol. Userland owns the trademark, and he has made it clear that he wants to prevent dilution of the name XML-RPC. I have encountered many ways to transmit complex data in XML-RPC messages while conforming to the spec, so show me the details! :)
-- Ryan Hoegg ISIS Networks http://www.isisnetworks.net