Dr Scofield kirjoitti: >> operations involved (i.e. the load oar "function" specifies how the oar file >> is transported over the wire) so the interface is truly remotable. If you >> > i've to agree on that. i'd started something like that, but haven't really > made > any headway due to lack of time. being a pythonista i tend to look at things > through python glasses: invoking an XmlRpc method is easy, doing the same > thing > with REST is a pain. >
Where is the pain with REST? Am just curious to learn more, have written some REST servers and simple clients to them in Python, but used XML-RPC and SOAP too. Haven't written complex REST clients (yet). Invoking a method is of course trivial, just a http get, but does it get difficult with parameters then? http://code.google.com/p/python-rest-client/wiki/Using_Connection says: conn.request_post("/upload", body=body) is it difficult to put a oar file in the body? or are you talking about defining types, having the signatures of the methods etc explicit in some interface description? Like with SOAP it was kinda handy with soappy that what you get to py is normal objects with functions with __doc__ about the parameter vals and return vals etc. > DrS/dirk > ~Toni _______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
