I have some thoughts but need to finish a few other things first. I kind of want something a bit more barebones that speaks both client and server so I can embed it into the server and help prevent bitrot. Then another wrapper around that which becomes the external client.
At the same time I'd like to fix some protocol problems... Been bothering me for a long time. Might be a good opportunity to kill a flock of birds. On Fri, 25 Aug 2017, Brian Aker wrote: > I am not really sure where to go with libmemcached right now. > > Its design shows the age in which it was built. > > > On Aug 25, 2017, at 00:52, dormando <dorma...@rydia.net> wrote: > > > > Pretty sure Frank was asking about server implementations of memcached in > > python. > > > > As per that, I've only ever seen people create those for eduational > > purposes. Not aware of something anyone runs in production. What do you > > need it for? > > > > As per libmemcached being idle; I've noticed and am hoping to be able to > > work on it this year. > > > > -Dormando > > > > On Thu, 24 Aug 2017, Min-Zhong "John" Lu wrote: > > > >> We use pylibmc. Fairly stable and built-in handling of multi-server key > >> distribution. The disadvantage of pylibmc (and many other client > >> libraries) lies > >> in its dependency on libmemcached, which has seen little activity for > >> quite some while, which in turn hinders utilization of new memcached > >> commands; IIRC > >> one example is the GAT command. > >> Frankly the situation is the same for any python client library depending > >> on libmemcached for the actual underlying protocol/network communication. I > >> believe there's essentially no way to work around it except for > >> patching/building your own libmemcached. > >> > >> Cheers, > >> - Mnjul > >> > >> On Thursday, August 24, 2017 at 2:55:13 PM UTC-7, Frank Wang wrote: > >> Hi, > >> I know there are a bunch of Python versions of memcached clients. Does > >> anyone know of any good/stable Python implementations of the memcached > >> server? > >> > >> Thanks, > >> Frank > >> > >> -- > >> > >> --- > >> You received this message because you are subscribed to the Google Groups > >> "memcached" group. > >> To unsubscribe from this group and stop receiving emails from it, send an > >> email to memcached+unsubscr...@googlegroups.com. > >> For more options, visit https://groups.google.com/d/optout. > >> > >> > > > > -- > > > > --- > > You received this message because you are subscribed to the Google Groups > > "memcached" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to memcached+unsubscr...@googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. > > -- > > --- > You received this message because you are subscribed to the Google Groups > "memcached" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to memcached+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
