The object interface is intended to be similar to the Python interface to Danga Interactive's Memcache. The equivalent functions are for convenience, since the object doesn't need to maintain state, like a connection to a particular Memcache server. No other differences that I'm aware of. -- Dan
On Mon, Oct 27, 2008 at 7:15 AM, pr3d4t0r <[EMAIL PROTECTED]> wrote: > > Greetings, > > Is the reason there are two Memcache APIs, one for the Memcache > client, one for calling the functions directly, just having one that's > more OO than the other? Are there any use-cases for preferring one > vs. the other? It looks at first glance like Client is just a wrapper > around the functions and doesn't provide any additional features. > > Are there any use cases where one is preferred over the other? > > (I'm thinking of the differences between running db.Query vs. GqlQuery > and how they execute queries. Maybe there is something like that in > play here that I've missed.) > > Thanks in advance and have a fantastic week, > > E > http://www.istheserverup.com > http://www.teslatestament.com > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
