Anyone writing or planning to write a REST API for memcached?
If no such plan, I would be interested in writing a REST API.
Any suggestions, comments welcome.
Jul 28, 2010 at 8:43 AM, jsm wrote:
> Anyone writing or planning to write a REST API for memcached?
> If no such plan, I would be interested in writing a REST API.
> Any suggestions, comments welcome.
>
Regards,
>
> Gavin
>
>
> On Wed, Jul 28, 2010 at 8:43 AM, jsm wrote:
>
>> Anyone writing or planning to write a REST API for memcached?
>> If no such plan, I would be interested in writing a REST API.
>> Any suggestions, comments welcome.
>>
>
>
terse in comparison to the ASCII
> > protocol. In addition netcat or telnet works as good as curl for drop dead
> > simplicity. Don't get me wrong, it would be neat, but shouldn't be
> > considered in moderately well used memcached environments.
>
> > Regards,
>
> &
Gavin,
You are right about the overhead and also saw that API's exist for
most of the languages as well.
I thought REST API would make memcached language agnostic.
I would like to hear from the community if the REST API should be
pursued or not?
On Jul 28, 7:43 pm, "Gavin M. Roy"
On Wed, Jul 28, 2010 at 11:37 AM, jsm wrote:
> > What is the value-add you are looking from the RESTful version of the
> > memcached API?
>
> Basically to be able to use without binding to any particular
> language.
>
Not to push too hard on his, but the ascii protocol is simple and easy to
impl
verhead and also saw that API's exist for
> most of the languages as well.
> I thought REST API would make memcached language agnostic.
> I would like to hear from the community if the REST API should be
> pursued or not?
>
> On Jul 28, 7:43 pm, "Gavin M. Roy"
On 7/28/2010 10:16 AM, jsm wrote:
Gavin,
You are right about the overhead and also saw that API's exist for
most of the languages as well.
I thought REST API would make memcached language agnostic.
I would like to hear from the community if the REST API should be
pursued or not?
I'm
ul 28, 2010 at 12:03 PM, Les Mikesell wrote:
> On 7/28/2010 10:16 AM, jsm wrote:
>
>> Gavin,
>> You are right about the overhead and also saw that API's exist for
>> most of the languages as well.
>> I thought REST API would make memcached language agnostic.
>
memcached and its own binary
protocol as well: http://1978th.net/tokyotyrant/spex.html#protocol
On Wed, Jul 28, 2010 at 12:03 PM, Les Mikesell mailto:lesmikes...@gmail.com>> wrote:
On 7/28/2010 10:16 AM, jsm wrote:
Gavin,
You are right about the overhead and also
It speaks memcached and its own binary
>> protocol as well: http://1978th.net/tokyotyrant/spex.html#protocol
>>
>> On Wed, Jul 28, 2010 at 12:03 PM, Les Mikesell > <mailto:lesmikes...@gmail.com>> wrote:
>>
>>On 7/28/2010 10:16 AM, jsm wrote:
>>
>
ght
>>> I recommend Tokyo Tyrant? It speaks memcached and its own binary
>>> protocol as well: http://1978th.net/tokyotyrant/spex.html#protocol
>>>
>>> On Wed, Jul 28, 2010 at 12:03 PM, Les Mikesell >> <mailto:lesmikes...@gmail.com>> wrote:
>>
On 7/28/2010 1:43 PM, Marc Bollinger wrote:
"and some of them have inherent http capability and aren't used enough
to care about that last 10% efficiency when it means rewriting a bunch
of code with new libraries to get it."
But you're..._adding_ support for memcached to that system. If this wer
y protocol is very terse in comparison to the ASCII
>> > protocol. In addition netcat or telnet works as good as curl for drop dead
>> > simplicity. Don't get me wrong, it would be neat, but shouldn't be
>> > considered in moderately well used memcached environ
GET request, minimal request headers and minimal response
> >> > headers. The binary protocol is very terse in comparison to the ASCII
> >> > protocol. In addition netcat or telnet works as good as curl for drop
> >> > dead
> >> > simplicity. Don't ge
gt;> > bytes by
> > >> > the HTTP GET request, minimal request headers and minimal response
> > >> > headers. The binary protocol is very terse in comparison to the ASCII
> > >> > protocol. In addition netcat or telnet works as good as curl for drop
> > >> > dead
> > >> > simplicity. Don't get me wrong, it would be neat, but shouldn't be
> > >> > considered in moderately well used memcached environments.
>
> > >> > Regards,
>
> > >> > Gavin
>
> > >> > On Wed, Jul 28, 2010 at 8:43 AM, jsm wrote:
>
> > >> >> Anyone writing or planning to write a REST API for memcached?
> > >> >> If no such plan, I would be interested in writing a REST API.
> > >> >> Any suggestions, comments welcome.
base the 100
> bytes by
> > >> > the HTTP GET request, minimal request headers and minimal response
> > >> > headers. The binary protocol is very terse in comparison to the
> ASCII
> > >> > protocol. In addition netcat or telnet works as good as curl for
> drop dead
> > >> > simplicity. Don't get me wrong, it would be neat, but shouldn't be
> > >> > considered in moderately well used memcached environments.
> >
> > >> > Regards,
> >
> > >> > Gavin
> >
> > >> > On Wed, Jul 28, 2010 at 8:43 AM, jsm wrote:
> >
> > >> >> Anyone writing or planning to write a REST API for memcached?
> > >> >> If no such plan, I would be interested in writing a REST API.
> > >> >> Any suggestions, comments welcome.
>
7;s a
> rough 100
> > > >> > byte overhead per request over the ASCII protocol. I base the 100
> bytes by
> > > >> > the HTTP GET request, minimal request headers and minimal response
> > > >> > headers. The binary protocol is very terse in comparison to the
> ASCII
> > > >> > protocol. In addition netcat or telnet works as good as curl for
> drop dead
> > > >> > simplicity. Don't get me wrong, it would be neat, but shouldn't
> be
> > > >> > considered in moderately well used memcached environments.
> >
> > > >> > Regards,
> >
> > > >> > Gavin
> >
> > > >> > On Wed, Jul 28, 2010 at 8:43 AM, jsm wrote:
> >
> > > >> >> Anyone writing or planning to write a REST API for memcached?
> > > >> >> If no such plan, I would be interested in writing a REST API.
> > > >> >> Any suggestions, comments welcome.
>
t; >> > bytes by
>> >> > the HTTP GET request, minimal request headers and minimal response
>> >> > headers. The binary protocol is very terse in comparison to the ASCII
>> >> > protocol. In addition netcat or telnet works as good as curl for drop
>> >> > dead
>> >> > simplicity. Don't get me wrong, it would be neat, but shouldn't be
>> >> > considered in moderately well used memcached environments.
>>
>> >> > Regards,
>>
>> >> > Gavin
>>
>> >> > On Wed, Jul 28, 2010 at 8:43 AM, jsm wrote:
>>
>> >> >> Anyone writing or planning to write a REST API for memcached?
>> >> >> If no such plan, I would be interested in writing a REST API.
>> >> >> Any suggestions, comments welcome.
he HTTP protocol overhead? REST/HTTP would add ~75Mbps of
> >> >> > additional traffic at 100k gets per second by saying there's a
> rough 100
> >> >> > byte overhead per request over the ASCII protocol. I base the 100
> bytes by
> >> >> > the HTTP
there's a
> > rough 100
> > >> >> > byte overhead per request over the ASCII protocol. I base the 100
> > bytes by
> > >> >> > the HTTP GET request, minimal request headers and minimal response
> > >> >> > headers. The binary protocol is very terse in comparison to the
> > ASCII
> > >> >> > protocol. In addition netcat or telnet works as good as curl for
> > drop dead
> > >> >> > simplicity. Don't get me wrong, it would be neat, but shouldn't be
> > >> >> > considered in moderately well used memcached environments.
>
> > >> >> > Regards,
>
> > >> >> > Gavin
>
> > >> >> > On Wed, Jul 28, 2010 at 8:43 AM, jsm wrote:
>
> > >> >> >> Anyone writing or planning to write a REST API for memcached?
> > >> >> >> If no such plan, I would be interested in writing a REST API.
> > >> >> >> Any suggestions, comments welcome.
On 7/29/2010 8:54 AM, j.s. mammen wrote:
Folks, lets not get bogged down by REST defined by Roy Fielding in
2000.
My question was simple.
Here it is again, rephrased.
Do we need to implement a memcached layer whereby we can access the
cached objects by using HTTP protocol. Here is an example o
On Thu, Jul 29, 2010 at 6:54 AM, j.s. mammen wrote:
> Folks, lets not get bogged down by REST defined by Roy Fielding in
> 2000.
>
> My question was simple.
> Here it is again, rephrased.
>
> Do we need to implement a memcached layer whereby we can access the
> cached objects by using HTTP proto
Roy <
> g...@myyearbook.com>
> > > wrote:
> >
> > > >> >> > Why add the HTTP protocol overhead? REST/HTTP would add
> ~75Mbps of
> > > >> >> > additional traffic at 100k gets per second by saying there's a
> > > rough 100
> > > >> >> > byte overhead per request over the ASCII protocol. I base the
> 100
> > > bytes by
> > > >> >> > the HTTP GET request, minimal request headers and minimal
> response
> > > >> >> > headers. The binary protocol is very terse in comparison to the
> > > ASCII
> > > >> >> > protocol. In addition netcat or telnet works as good as curl
> for
> > > drop dead
> > > >> >> > simplicity. Don't get me wrong, it would be neat, but
> shouldn't be
> > > >> >> > considered in moderately well used memcached environments.
> >
> > > >> >> > Regards,
> >
> > > >> >> > Gavin
> >
> > > >> >> > On Wed, Jul 28, 2010 at 8:43 AM, jsm
> wrote:
> >
> > > >> >> >> Anyone writing or planning to write a REST API for memcached?
> > > >> >> >> If no such plan, I would be interested in writing a REST API.
> > > >> >> >> Any suggestions, comments welcome.
>
>> values (e.g. hashes, lists, etc.) -- is that what you meant?
>> >
>> > > >> Aaron
>> >
>> > > >> >> Regards,
>> > > >> >> Rajesh Nair
>> >
>> > > >> >> On Wed, Jul 28, 2010 at 8:13 PM, Gavin
gt;
>> > > >> I read this as requesting memcached native support for structured
>> > > >> values (e.g. hashes, lists, etc.) -- is that what you meant?
>> >
>> > > >> Aaron
>> >
>> > > >> >> Regards,
>> >
On Thu, 29 Jul 2010, j.s. mammen wrote:
> Folks, lets not get bogged down by REST defined by Roy Fielding in
> 2000.
>
> My question was simple.
> Here it is again, rephrased.
>
> Do we need to implement a memcached layer whereby we can access the
> cached objects by using HTTP protocol. Here i
27 matches
Mail list logo
