[appengine-java] Re: Namespace design issues

2010-09-28 Thread Frederik Pfisterer
@Mouseclicker and John Patterson: To solve your problem in the meanwhile consider a meta-model of a Tenant in the default namespace. Each tenant entity should have a namespace field, plus whatever information you want it to hold about your tenant. You can then enforce

[appengine-java] Re: Namespace design issues

2010-09-27 Thread Mickey Kataria (Google Employee)
On Sep 24, 5:55 am, Mouseclicker jens.h...@googlemail.com wrote: I wanted to start a discussion about lifecycle and threading behavior of the NamespaceManager. Much of this has been answered meanwhile in another thread:http://groups.google.com/group/google-appengine-java/browse_thread/th...

[appengine-java] Re: Namespace design issues

2010-09-27 Thread Vikas Hazrati
more details about the namespace behavior as we observed here http://thoughts.inphina.com/2010/09/16/multi-tenancy-in-google-app-engine-scope-of-namespacemanager/ On Sep 24, 7:57 am, John Patterson jdpatter...@gmail.com wrote: On 24 Sep 2010, at 02:55, Mouseclicker wrote: API. The need to

[appengine-java] Re: Namespace design issues

2010-09-24 Thread Robert Lancer
What about the ability to move an entity to a namespace? On Sep 23, 10:57 pm, John Patterson jdpatter...@gmail.com wrote: On 24 Sep 2010, at 02:55, Mouseclicker wrote: API. The need to set and later reset a global setting is dangerous and error-prone. Probably that's what Guillaume mentions