OK - Thanks, Joseph for helping understand the role of the Utilities project.
A final question is the difference / compatibility between the Helper project, and the Patch project. Currently, I have completed some work on a project which was started in an environment with django .97 and the Helper. Now, I'd like to establish a foundation for the longer term. There is a bunch of rearranging I need to do to my code; I want to move to django 1.0; and I want to have non-Google login/ authentication. After research, I get the impression that the Patch serves my needs better than the Helper. It has zipped Django 1.0 implemented. It seems to have better support for authentication than the Helper. And in general, it appears that it is more substantial in terms of active development, than Helper is. Helper seems like it has slowed down a bit. It's last release was in early August. So my understanding is: 1. I should choose *either* Helper or Patch - not both. 2. It appears that Patch has better support for implementing authentication. 3. It appears that Patch is reliable. Is my analysis correct? Sorry to belabor the point. Maybe someone else will get value from this thread, too. :) On Oct 22, 5:04 am, Waldemar Kornewald <[EMAIL PROTECTED]> wrote: > On Oct 22, 3:32 am, "[EMAIL PROTECTED]" > > <[EMAIL PROTECTED]> wrote: > > utilities is just a bunch of, well, utilities, to make working with > > appengine easier, and is not django specific at all. It started > > because I recognized that there was no session api for appengine at > > all. Both helper and patch have gotten Django sessions working, and > > I'm not sure what level of support they offer for cache in django. I > > created appengine-utilities specifically to handle sessions and cache > > the best possible way on appengine, taking advantage of memcache to > > provide the best performance. > > Appenginepatch allows to use Django's memcache backend, so everything > should just work. > > Apart from the goal of making Django work seamlessly, appenginepatch > also provides a library of utility functions/extras. For example, our > most recent addition is a prefetcher for reference properties which > could help speed up your code. > > Just take a look at the (uhm, minimalistic :) > documentation:http://code.google.com/p/app-engine-patch/wiki/Documentation > > Bye, > Waldemar Kornewald --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
