On 12/10/2009 05:46 PM, Pavel Shramov wrote:
> On Thu, Dec 10, 2009 at 05:06:09PM +0100, Romain François wrote:
>>> I'm using method name encoded in query part of URL like 
>>> /base/url?Service.Method
>> That seems odd. Why not /base/url?service=Service&method=Method instead ?
> For simplicity (from my point of view). Query string is here only to identify 
> method
> to call and not to pass parameters to it. So why to bother?

What about then if you want to control the kind of output that is 
returned back (pb or json). I would then add &encoding=pb or 
&encoding=json. How do you do this ?

I don't have any strong opinions. I think the best format is :


where "service" is the service full name, and "method" the method name 
within the service.

>>> Also it's seem useful to provide Content-Type to distinguish between 
>>> different
>>> encodings of message (for example JSON).
>> Yep. Will add this.
> I'm using application/x-protobuf here as protobuf-net does.
>> I will. So this makes 3 very similar http based protocols, but slightly
>> different. We should come to an agreement. :-)
> Definitely we have :) But it seem impossible :)
>               Pavel

Romain Francois
Professional R Enthusiast
+33(0) 6 28 91 30 30
|- http://tr.im/Gq7i : ohloh
|- http://tr.im/FtUu : new package : highlight
`- http://tr.im/EAD5 : LondonR slides


You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To post to this group, send email to proto...@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to