[Opensim-dev] ConsoleClient -pass option

[Dickson, Mike (ISS Software)]

Right, for example the load oar case is probably best handled with REST by adding a new verb and I including the OAR file in the body as you suggest.  But the current console code as best as I can tell would need to be augmented to do that.

My point is, if you want to make it easy for others to implement what is very likely an RPC like interface in the first place (which the console code is, IMO, it has "commands" that take parameters much like a function call/rpc call) then why not use XML/RPC in the first place and take advantage of the standardized wire format support and broad language support. 

But as you indicate, you certainly can do it w/REST, you just end up writing the parsers on both sides yourself.

Mike

-----Original Message-----
From: opensim-dev-bounces at lists.berlios.de [mailto:opensim-dev-bounces at lists.berlios.de] On Behalf Of Toni Alatalo
Sent: Wednesday, September 09, 2009 3:15 AM
To: opensim-dev at lists.berlios.de
Subject: Re: [Opensim-dev] ConsoleClient -pass option

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
Opensim-dev at lists.berlios.de
https://lists.berlios.de/mailman/listinfo/opensim-dev