Hi Nicolas, The memcached server doesn't do anything by itself, it caches whatever you put into it from your client applications, and that's it. Putting the client and the server in the same process is not possible, and also makes absolutely no sense whatsoever. The whole point of using memcached is that it is a distributed out-of-process networked cache that scales linearly.
/Henrik On Mon, Mar 4, 2013 at 12:53 PM, Nicolas Garcin < [email protected]> wrote: > Hi, > > I'm new to Memcached and I would like to understand the following points: > > * from what I read here > https://code.google.com/p/memcached/wiki/NewOverview, Memcached can not > only cache date from database but also cache data from API calls. Do you > know where I can find more information about how to configure/implement > Memcached so that it gets fed from an API call instead of a database? > > * do Memcached Client and Server have to live in 2 distinct processes or > would it be possible to embed Client and Server in the same process? > > Thanks, > Regards, > Nicolas > > > -- > > --- > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
