'noreply' over the wire

Peter J. Holzer hjp at hjp.at
Sun Nov 11 15:51:33 UTC 2007

On 2007-11-11 12:22:20 +0300, Tomash Brechko wrote:
> On Sat, Nov 10, 2007 at 11:15:29 -0800, Steven Grimm wrote:
> > Your application never streams requests to memcached, does it? If you  
> > don't do that, any performance impact of replies coming over the wire  
> > are pretty much overwhelmed by network latency. And if you *do* stream  
> > requests, then your noreply proposal (which as I understand it is more  
> > of a "sometimesreply" option) is 100% useless because it will be  
> > impossible for a client to know which errors / responses go with which  
> > requests.
> What do you mean by streaming?  How this can be done from
> Cache::Memcached?

Cache::Memcached (the perl module) doesn't provide a streaming interface
AFAICS, but it would be possible to add one without changing the
protocol. For example, you could register a callback function, and if
one is registered it doesn't wait for a reply but calls the callback
function if there is one. You would also want a method to wait for any
outstanding replies in this case. Or you could build something around an
event-loop (so somebody will probably now point out that Danga already
has an event-based, streaming-capable interface to memcached).


   _  | Peter J. Holzer    | It took a genius to create [TeX],
|_|_) | Sysadmin WSR       | and it takes a genius to maintain it.
| |   | hjp at hjp.at         | That's not engineering, that's art.
__/   | http://www.hjp.at/ |	-- David Kastrup in comp.text.tex
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.danga.com/pipermail/memcached/attachments/20071111/e23eacd5/attachment.pgp

More information about the memcached mailing list