[google-appengine] Re: Cannot add acces from Google Apps domain to Google App Eninge application.

2012-05-25 Thread Jeroen Benckhuijsen
d be added to the docs I guess, or perhaps better checking in the AppEngine app creation forms... Hope this helps for someone Op woensdag 23 mei 2012 14:17:46 UTC+2 schreef Jeroen Benckhuijsen het volgende: > > Thanks, > > adding google-developers works fine. Switching back to no-aut

[google-appengine] Re: Cannot add acces from Google Apps domain to Google App Eninge application.

2012-05-23 Thread Jeroen Benckhuijsen
> Business, try contacting apps support. > > On Wednesday, May 23, 2012 1:10:20 PM UTC+2, Jeroen Benckhuijsen wrote: >> >> Hi Alex, >> >> Thanks for the reply. With regards to the auth page, I was referring to >> the last section ("Configuring Google A

[google-appengine] Re: Cannot add acces from Google Apps domain to Google App Eninge application.

2012-05-23 Thread Jeroen Benckhuijsen
click "Activate this service". Thanks, Jeroen Op woensdag 23 mei 2012 12:09:50 UTC+2 schreef alex het volgende: > > Jeroen, > > First link describes authentication method, how and who you want to be > able to sign in (assuming you are going to use it later in your app via

[google-appengine] Cannot add acces from Google Apps domain to Google App Eninge application.

2012-05-23 Thread Jeroen Benckhuijsen
talking about, what am I doing wrong? Thanks. Jeroen -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/G5lNrzXhFlIJ. To post to this gro

[google-appengine] Re: Why Google AppEngine sucks

2009-09-28 Thread Jeroen
el properties? This can make an > enormous difference. > > On Sep 27, 1:37 am, Jeroen wrote: > > > Biggest problem: The datastore is deadslow and uses indane amounts of > > cpu. I found 2 ways around it, backwards ones imho, but if it works, > > it works. > >

[google-appengine] Re: Why Google AppEngine sucks

2009-09-26 Thread Jeroen
Biggest problem: The datastore is deadslow and uses indane amounts of cpu. I found 2 ways around it, backwards ones imho, but if it works, it works. Maybe my usecase is unique, as it involves frequent updates to the data (10k records) stored. 1st solution: Only update the datastore after 2 new up