xmlrpclib and mx.DateTime

[Chuck Esterbrook]

On Wednesday 30 January 2002 05:26 pm, Brian Quinlan wrote:
> Chuck wrote:
> > Next, xmlrpclib.py complained about None (I'm sending over a dict
> > of information with various contents). So I put that in.
> >
> > Now it complains that my longs are too big.
> >
> > At this point I've decided XML-RPC is not for me. I'll enhance
> > Webware to include a PickleRPCServlet to complement it's existing
>
> XMLRPCServlet.
>
> > Those wanting something Pythonic can use the former, and those
> > wanting XML-RPC compliance can use the latter.
>
> I'm not sure what you were expecting here. The XML-RPC spec has a
> list of supported types (http://www.xmlrpc.com/spec) and there is no
> obvious mapping between Python longs and None to those types.
>
> You should probably look at the spec first and then figure out what
> types you want to use. And consider the pain that will be involved
> for users of other languages. For example, how is the C/Perl/PHP user
> supposed to deal with a 500 digit integer? If you expect the value to
> be opaque, just pass/return it as a string.
>
> Cheers,
> Brian

You're right: I didn't closely examine XML RPC for my purposes. Since 
Webware already supported it, I charged ahead to see if it would do the 
job that I needed.

Subsequently, I'm cooking up a DictRPCServlet which has Pythonic 
convenience: anything that can be pickled can be passed to and fro. No 
special "wrappers" are needed.

This lets me use my existing code without changes, which is more 
important for me than language independence.

As to how C, Perl and PHP users manage to get along, I have no idea.
;-)


-Chuck