On Mar 11, 4:01 pm, nwp <[email protected]> wrote:
> I was kicking around some ideas today, and I think what I want to do > is use socketpair() to create an anonymous unix socket, and run > memcached as a child process and have it listen on one end. I might > want several instances, so I don't really want to specify a tcp port > or create socket files to clean up later. Adding a flag to let it > listen on stdin would suit my needs nicely. > > Does this sound reasonable or useful to anyone else? I could hack > something up and post a patch. Going over the network means you effectively get more memory than you can have in a single box and having it persistent across restarts. If you're not going to get one of these benefits, then it seems like you'd really be best off extracting the data structures from memcached and using them as an in-process cache.
