Ah, the the DTD (or Schema) for XML-RPC is not really the point. For example, we use xmlrpc for factory automation data to send data from the server to an applet. Each returned value is an Array containing (at least) the value, timestamp, quality, etc. On each request you may get one or more of these, so the method returns an array of arrays. Most of the time we'll drop values if you didn't ask for them fast enough, but sometimes we'll send every value (alarms for instance), then you have an array of arrays of arrays. And occasionally we'll throw in some more data just for fun (colors, extra dates, some strings, etc. etc.). So, simplying saying that we return an "array" is not useful. It could be described in a DTD, that is, I think that one could describe it in a DTD (_one_, not necessarily me), but it would be a challenge to then convert that to C++.
As soon as I get a chance I'll dig through the links to IDL definitions Michael Dupont sent. BUT I think the problem is more complex than I'm willing to tackle. Jim On 2002.03.08 11:52:51 -0700 John Wilson wrote: > > ----- Original Message ----- > From: "Daniel Rall" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, March 08, 2002 6:41 PM > Subject: Re: Interceptors/Introspection patch > > > > Jim Redman <[EMAIL PROTECTED]> writes: > [snip] > > > > It would be fairly easy to write a DTD against the XML-RPC spec. I > > wouldn't be surprised if someone hadn't done it already (but I haven't > > looked). The DTD would be the best cross language description of the > > available interface. > > There's a DTD at http://www.ontosys.com/xml-rpc/xml-rpc.dtd > > There's a DTD and W3C Schema at > http://www.ibiblio.org/xml/books/xmljava/chapters/ch02s05.html#d0e2848 > > The DTD is easy to do but not particularly useful. The Schema is more > interesting. > > John Wilson > The Wilson Partnership > http://www.wilson.co.uk > -- Jim Redman (505) 662 5156 http://www.ergotech.com
