Difference between Protocol Buffers and HTTP interface

Hi there, What is the difference between Protocol Buffers and HTTP interface? And how and when we should select one of them for our applications? Thanks in advance, Alek. ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mai

Re: Difference between Protocol Buffers and HTTP interface

Protobuf is much much faster as it is a binary protocal. HTTP is simpler for debugging and so on. There are some stuff only available for HTTP, such as setting bucket prop and secure connections. Cheers, Shuhao On Fri, Jul 6, 2012 at 9:58 AM, Alek Morfi wrote: > Hi there, > > What is the diff

Re: Difference between Protocol Buffers and HTTP interface

Protocol Buffers are compact and fast and exposes most functionality. All functionality (AFAIK) is available via the HTTP interface but it's not what anyone would call fast. The better clients hide this from you and let you worry about writing software. --- Jeremiah Peschka - Managing Directo

Re: Pass json as argument to mapreduce

Venki, >From what I gather you're trying to specify arguments directly as objects in >the function's argument list? You reference the arg that's passed into the >MapReduce request by declaring a third parameter variable, not by specifying >an object: function(value, keydata, arg) {doSomethingWi