RE: New release of phpxmlrpc and EXTRAS package

> ...
> 
> Here are some documents that describe it:
> http://xins.sf.net/docs/protocol/
> http://xins.sf.net/docs/ar01s22.html#N10CC3
> http://xins.sf.net/restrpc.html
> 
> Improved stand-alone documentation is one of our next priorities.
> 

Ok, the current docs are more than I hoped for.
There are some problems with implementing it on top of phpxmlrpc tough:

- in xmlrpc and jsonrpc the input parameters are not named but positional.
Is there room for defining a standard encoding of those (param1,
param2, etc... vs. 'any param name will do, we only take the position'
- which looks very misunderstanding prone)?
Otoh I could code a subclass of server and client classes that use php
'named arrays' instead of 'numeric arrays' to represent paremeters,
and it would be mostly fine, except for implementing multi-protocol
servers.

- in xmlrpc the error is represented by both number and string.
I think this can be easily solved prepending the error code to the
error string, unless xins clients rely on finding the exact error
string specified in the docs, eg. "_InternalError". Or a data element
could be used to hold the xmlrpc error code and msg...

- how are recursive parameters encoded in the request?

apart from that, it should not be hard: an xmlrpc response, with its
single param value, looks like a valid xins response (provided that
the "name" attribute is optional, which the spec does not state clearly)

Bye
Gaetano





 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/xml-rpc/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/