Multi-Interface Patch

[dormando]

Dustin Sallings wrote:
> 
> On Feb 13, 2008, at 23:02, Brian Aker wrote:
> 
>> As to order, memcached has to feed you keys back in the order you sent
>> them, or you have to keep a map of key to opaque ID. That map is
>> expensive. Dormando is saying that the end user should keep this, but
>> you believe it belongs in the library.
> 
>     I just don't understand why you think you need a map.  An array of
> char* is perfectly sufficient.
> 
>     Likewise, order doesn't matter.  They do come back in the same
> order, but it's not guaranteed.  We could guarantee it, I suppose.  I
> just don't see the gain.
> 

For what it's worth; I don't really care if the user does it or not; I
was just pointing out that the user has an implicit mapping for this.
Which may or may not be utilized here. It does make sense for the
library to do it.

-Dormando