[google-appengine] Re: appcfg Server Error 500
For normal webdev yes its ok, but in the context of facebook apps we need to supply fbml and receive post requests from/to facebook servers. And I can no way do this on my localmachine. So I have to upload every change to google appenine and ask facebook servers to interact with the facebook app on the appengine. On Dec 20, 9:47 am, Ben Bishop leo...@gmail.com wrote: Install the SDK on your local machine so you can develop, test and debug. When you've got a stable production version ready, deploy to App Engine. It's well worth the effort of installing the SDK - you'll find it a lot faster process of developing your apps. On Dec 20, 11:05 am, samba cooldudevam...@gmail.com wrote: I have been learning and writing appengine based facebook apps. The problem is you have to upload your code using appcfg every time you make a small modification. And today I ran out of quota of using --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: appcfg Server Error 500
Found a fix, started using dyndns and pointed it to my local appengine sdk dev server. On Dec 20, 1:46 pm, samba cooldudevam...@gmail.com wrote: For normal webdev yes its ok, but in the context of facebook apps we need to supply fbml and receive post requests from/to facebook servers. And I can no way do this on my localmachine. So I have to upload every change to google appenine and ask facebook servers to interact with the facebook app on the appengine. On Dec 20, 9:47 am, Ben Bishop leo...@gmail.com wrote: Install the SDK on your local machine so you can develop, test and debug. When you've got a stable production version ready, deploy to App Engine. It's well worth the effort of installing the SDK - you'll find it a lot faster process of developing your apps. On Dec 20, 11:05 am, samba cooldudevam...@gmail.com wrote: I have been learning and writing appengine based facebook apps. The problem is you have to upload your code using appcfg every time you make a small modification. And today I ran out of quota of using --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: GqlQuery bind method - is it safe to share the same query instance between requests?
Be aware that the value of a global variable is not known at the start of a request. It could be the value from the previous request if the interpreter was already warm/running. It would be the initial value if the interpreter was started cold. Why not put the GQL object in the request handler self.gql1= GqlQuery(...) or just a local variable? How often do you bind new values to the query for each request? 2008/12/17 Alex Epshteyn alexander.epsht...@gmail.com: Ah, I see. It's safe because a new request will not be processed by the same instance of the python interpreter until the previous request has fully completed, right? Thanks, Ryan! On Dec 16, 7:37 pm, Ryan Barrett goo...@ryanb.org wrote: hi alex! you're right to be cautious, but happily, requests are not handled by different threads. our python interpreters are single threaded, and handle only a single request at a time. more: http://code.google.com/appengine/docs/python/sandbox.htmlhttp://groups.google.com/group/google-appengine/browse_thread/thread/... given that, you don't need to worry about concurrent accesses to the query global variable, so this should be safe. even better, fetch() re- runs the query from the beginning, so if the parameters are the same across requests, you don't even need to bind() each time. --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: failed to connect to localhost
I can get helloworld to work from the command prompt... just not localhost. app.yaml was copied from the example and used notepad to author. It seems like it runs ok but localhost does not work. If I change to incorrect syntax in app.yaml, I do get an error message when I try to run from cmd. I did try to copy the files to new_project_template but that did not do the trick. I also tried running the app in new_project_template. No luck. Forgot to mention before posting, but I did install PIL. I tried over a span of a week or so with several full reboots. Anyway, I stopped trying for a couple of weeks and then came back to it. Magically, it works now. On Mon, Nov 24, 2008 at 8:30 AM, A. TNG tang.j...@gmail.com wrote: On Fri, Nov 21, 2008 at 9:37 PM, Brian bdele...@gmail.com wrote: Helloworld.py contents: print 'Content-Type: text/plain' print '' print 'Hello, world!' Hi Brian, Are you sure your helloworl.py is correct? Check the appengine installation folder (C:\Program Files\Google\google_appengine). There is a folder naming new_project_template. Just open your command line window and change folder to C:\Program Files\Google\google_appengine\new_project_template. Then execute dev_appserver.py .. At last, access http://localhost:8080/ with firefox/IE or whatever. You will get your helloworld. -- Best Regards, TANG Jiyu (Blog: http://jiyu.wordpress.com.cn) --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: 1 application, multiple datastores
You can just use separate tables for each customer. I haven't tried it myself yet, so I don't know all the problems you will have to deal with. Of course than the dynamic handling with class names for the models gets more complex (and I am not aware of any existing framework for that) and porting existing python web apps to appengine also gets much more complicated. An easier approach is just to prepend keys with a customer identifier, but then you still have the possibility to query on all customers, and if things go wrong, possibly breaking the segregation. I do not know how Google has solved this problem at Google Apps for your domain, but of course would love to hear how they have done it. regards Roberto On Dec 20, 10:09 am, hawkett hawk...@gmail.com wrote: This is a required feature for a commercial SaaS/PaaS offering, and is not the same as Bill's issue in previous thread entry (Issue 06). This discussion can help you understand why - http://blogs.zdnet.com/service-oriented/?p=1236 as can bugs like this http://forum.assembla.com/forums/3/topics/256 We need it to be as close to impossible for one customer's data to be made available to another customer, without having to deploy a new instance of the application. Let's call it data segregation. A concept of 'virtual instances' would be a possible approach - so we can aggregate billing quota stats across multiple instances, and also identify individual instance billing and quota. Use Case: 1. Customer comes to my site 2. Clicks the 'Sign up now' button 3. Enters their details 4. Starts using the system You can't get a more 'core' use-case than that for a SaaS/PaaS platform. Notice there is no requirement to deploy a new version of the app for this customer. The system spawns a virtual instance of the app - or at least allows mapping a single datastore partition to the authenticated entity. You coudl extend it by allowing multiple datastores per authenticated entity and choosing the appropriate one at authentication time. The key requirement is that we can on-board a customer without manual intervention, and accurately understand a single customer's usage profile. Data corruption for one customer does not equal data corruption for another customer. This feature is in some ways the *opposite* of the feature request identified by the previous poster - we *do not* want to be able to access data in another partition - even if we tried to, and especially via a bug in our code. Here it is, please star it :) http://code.google.com/p/googleappengine/issues/detail?id=945 Any chance someone at Google has something to say about it? Thanks, Colin On Dec 20, 5:17 am, Ben Bishop leo...@gmail.com wrote: Not sure what you mean by in case something happens - your app and its datastore is served by the same network of servers that serve other apps, so separate accounts won't help, (unless you're going against the Terms of Service, running the risk of having an account banned). One App Engine account can have 10 apps, each with its own datastore and quota. You could deploy a single app's codebase to multiple app slots, simply by changing the app name in the app.yaml for each instance. That way you could test on a production test app or one of your client apps before rolling out updates to your other client apps. You still maintain a single codebase, each client app has its own datastore, and you can control updates. On Dec 20, 2:05 am, GTako tako.ko...@gmail.com wrote: Hi, is it possible to maintain under 1 application, multiple datastores that each datastore will be as if it is different app engine account? for example: i have a web application that should serve 2 companies, A and B. I would want to open a google app engine account for the web application files. the datastores for A and B could be 2 different deployments under the same app engine account or under seperate accounts. now assume i have N companies. what should i do? the reason for seperation is that i dont want the datastores will be dependent and under same account in case soemthing happens. please advise. --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Django+Appengine vs Appengine
On Dec 15, 4:58 am, Bobby bobbysoa...@gmail.com wrote: In addition to this i'm seeing that the Django admin site has been replaced by the AppEngine data viewer which isn't as powerful or customizable right now, so i'm not seeing alot of reasons to use the Django framework (other than wanting to). What are the main advantages of using Django on the AppEngine? (i can see at least two disadvantages in having an additional layer and added configuration/maintenance). Well, that's exactly what I think of using Django in appengine. You don't get one of its most useful features (admin), and you have a bloated layer on top of App Engine. In my case, I use a lightweight and easier option called webpy. It is very similar to webapp, the built-in GAE framework, but more polished, simple and complete (actually, it was the inspiration behind webapp). Check it out: http://webpy.org Luis --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] How much time to give for each db query in order not to occur DeadlineExceededError
Too much db operations, it needs 10 seconds on my own computers to read the whole file to store in the datastore. But on the GAE, it occurs DeadlineExceededError. I gave 0.2 second for each db put(), it could work first but finally went wrong. I then gave 0.5 second and still could't solve the problem. How much time shall I give?? --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: GqlQuery bind method - is it safe to share the same query instance between requests?
The advantage of caching GqlQuery objects between requests is that it saves on having to compile the GQL for future requests. By storing it in a global and binding new values prior to calling, it gets compiled on the first request for the web server instance, and uses the pre-compiled version on subsequent requests. The only caveat is that you must remember to bind values prior to executing the query (calling fetch(), get() or using the iterator interface). If you call without binding, it might use values bound during a previous request. -- Dan On Sat, Dec 20, 2008 at 3:25 AM, djidjadji djidja...@gmail.com wrote: Be aware that the value of a global variable is not known at the start of a request. It could be the value from the previous request if the interpreter was already warm/running. It would be the initial value if the interpreter was started cold. Why not put the GQL object in the request handler self.gql1= GqlQuery(...) or just a local variable? How often do you bind new values to the query for each request? 2008/12/17 Alex Epshteyn alexander.epsht...@gmail.com: Ah, I see. It's safe because a new request will not be processed by the same instance of the python interpreter until the previous request has fully completed, right? Thanks, Ryan! On Dec 16, 7:37 pm, Ryan Barrett goo...@ryanb.org wrote: hi alex! you're right to be cautious, but happily, requests are not handled by different threads. our python interpreters are single threaded, and handle only a single request at a time. more: http://code.google.com/appengine/docs/python/sandbox.htmlhttp://groups.google.com/group/google-appengine/browse_thread/thread/. .. given that, you don't need to worry about concurrent accesses to the query global variable, so this should be safe. even better, fetch() re- runs the query from the beginning, so if the parameters are the same across requests, you don't even need to bind() each time. --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Django+Appengine vs Appengine
The MVC, self-contained, DRY approach offered by Django is what really sells it for me at this point (even with the reduced feature set on the AppEngine). I saw this great video from DjangoCon that really outlines this strength of Django: http://www.youtube.com/watch?v=A-S0tqpPga4feature=channel_page This promotes really good app design. There's alot of docs to go through to get Django running on the AppEngine (in particular if you're getting started with both), but once you have a couple of apps running then it's a breeze, i recommend it. Bobby On Dec 20, 10:36 am, luismgz luis...@gmail.com wrote: On Dec 15, 4:58 am, Bobby bobbysoa...@gmail.com wrote: In addition to this i'm seeing that the Django admin site has been replaced by the AppEngine data viewer which isn't as powerful or customizable right now, so i'm not seeing alot of reasons to use the Django framework (other than wanting to). What are the main advantages of using Django on the AppEngine? (i can see at least two disadvantages in having an additional layer and added configuration/maintenance). Well, that's exactly what I think of using Django in appengine. You don't get one of its most useful features (admin), and you have a bloated layer on top of App Engine. In my case, I use a lightweight and easier option called webpy. It is very similar to webapp, the built-in GAE framework, but more polished, simple and complete (actually, it was the inspiration behind webapp). Check it out:http://webpy.org Luis --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Can't manage applications, just keep getting put back on the start page.
Every time I create an application, I just end up back on the create application page. I create an application successfully, then boom, back to http://appengine.google.com/start I've successfully added applications to a friends account so I know I'm not doing something wrong. Of course I can't start from scratch with my google apps account (the account I should have used to begin with) because google won't let me use the same phone number again for verification. Any ideas? This is supposedly beta software, but I can't find any place to actually post bugs about it. Ridiculous. --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: How to fix pickling error
I had some problems while I tried storing in memcache a query object obtained with the fuction db.GqlQuery(...) and I've solved my issue with Entity.all() function... The same problem appears when I try to storing in memcache a python list that contains several Object that I've created. I've pybassed the problem but I think that it's good to get you to know this issue. --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Cannot create new application
I was listed as a developer on an existing application, so I signed in and SMS verified my account. Now I am trying to create my own application. When I click Create an Application I am brought again to the Verify your Account by SMS screen. However, when I type my phone number in, I am told The phone number has been sent too many messages or has already been used to confirm an account. Yes, I agree - my account! How can I get unstuck here and create an application? Thanks, -Miles --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] google gadgets for GAE developers
Are there plans to allow GAE developers to use google gadgets? Like the ones that run in iGoogle and elsewhere in the GOOG world? I would be interested in developing a google gadget that enabled use of youtube quick capture. I realize that page is iframe-able, but I would like something that looks as good as the Google Talk gadget. Thanks! Tim Nash Development Lead www.SanMateoWaveforms.com GAE: smw.appspot.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 google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Cannot create new application
I should add - I already have the one original app that I collaborate on in my menu, and I can manage it just fine. I just can't create a new one. -miles On Dec 20, 3:41 pm, mcrawfor miles.crawf...@gmail.com wrote: I was listed as a developer on an existing application, so I signed in and SMS verified my account. Now I am trying to create my own application. When I click Create an Application I am brought again to the Verify your Account by SMS screen. However, when I type my phone number in, I am told The phone number has been sent too many messages or has already been used to confirm an account. Yes, I agree - my account! How can I get unstuck here and create an application? Thanks, -Miles --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: google gadgets for GAE developers
hmm, I cant think of anything special that Google would need to do to allow GAE developers to use Gadgets. There is nothing stopping you making a gadget that talks to App Engine, or indeed embedding a gadget in a AppEngine hosted webpage. gadgets are estentially Javascript (and a bit of html/dhtml) - that runs client side. YouTube quick capture has nothing to do with AppEngine anyway. You would need to find out from the YouTube people if you could make a gadget from it. Or maybe reverse enginner the page http://uk.youtube.com/my_videos_quick_capture .. again nothing to do with AppEngine. 2008/12/20 Nash-t timna...@gmail.com: Are there plans to allow GAE developers to use google gadgets? Like the ones that run in iGoogle and elsewhere in the GOOG world? I would be interested in developing a google gadget that enabled use of youtube quick capture. I realize that page is iframe-able, but I would like something that looks as good as the Google Talk gadget. Thanks! Tim Nash Development Lead www.SanMateoWaveforms.com GAE: smw.appspot.com -- Barry - www.nearby.org.uk - www.geograph.org.uk - --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] get_by_key_name timeout!
12-19 06:34PM 51.839 Traceback (most recent call last): File /base/python_lib/versions/1/google/appengine/ext/webapp/ __init__.py, line 498, in __call__ handler.get(*groups) File /base/data/home/apps/[edited out]/1.329827330674031168/ helloworld.py, line 96, in get curuser=CellPhones.get_by_key_name(n:+number) File /base/python_lib/versions/1/google/appengine/ext/db/ __init__.py, line 837, in get_by_key_name return get(*keys) File /base/python_lib/versions/1/google/appengine/ext/db/ __init__.py, line 1032, in get entities = datastore.Get(keys) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 217, in Get raise _ToDatastoreError(err) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 1637, in _ToDatastoreError raise errors[err.application_error](err.error_detail) Timeout I understand that I get timeouts for put() operations, but what's the explanation for this one? --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Can't manage applications, just keep getting put back on the start page.
Do you use a Google Apps email account? In this case you need to go to this URL: http://appengine.google.com/a/YOURDOMAIN.COM/ On Dec 21, 5:22 am, Josh goo...@strongwords.org wrote: Every time I create an application, I just end up back on the create application page. I create an application successfully, then boom, back tohttp://appengine.google.com/start I've successfully added applications to a friends account so I know I'm not doing something wrong. Of course I can't start from scratch with my google apps account (the account I should have used to begin with) because google won't let me use the same phone number again for verification. Any ideas? This is supposedly beta software, but I can't find any place to actually post bugs about it. Ridiculous. --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: 1 application, multiple datastores
Neither of the cited discussions nor your comments explain why it's different that Bill's access to separate datastore request. In fact, his request is essentially at least allows mapping a single datastore partition to the authenticated entity. There are some issues with accounting, but if your app can do its accounting in the user's datastore, you get that too. On Dec 20, 5:09 am, hawkett hawk...@gmail.com wrote: This is a required feature for a commercial SaaS/PaaS offering, and is not the same as Bill's issue in previous thread entry (Issue 06). This discussion can help you understand why - http://blogs.zdnet.com/service-oriented/?p=1236 as can bugs like this http://forum.assembla.com/forums/3/topics/256 We need it to be as close to impossible for one customer's data to be made available to another customer, without having to deploy a new instance of the application. Let's call it data segregation. A concept of 'virtual instances' would be a possible approach - so we can aggregate billing quota stats across multiple instances, and also identify individual instance billing and quota. Use Case: 1. Customer comes to my site 2. Clicks the 'Sign up now' button 3. Enters their details 4. Starts using the system You can't get a more 'core' use-case than that for a SaaS/PaaS platform. Notice there is no requirement to deploy a new version of the app for this customer. The system spawns a virtual instance of the app - or at least allows mapping a single datastore partition to the authenticated entity. You coudl extend it by allowing multiple datastores per authenticated entity and choosing the appropriate one at authentication time. The key requirement is that we can on-board a customer without manual intervention, and accurately understand a single customer's usage profile. Data corruption for one customer does not equal data corruption for another customer. This feature is in some ways the *opposite* of the feature request identified by the previous poster - we *do not* want to be able to access data in another partition - even if we tried to, and especially via a bug in our code. Here it is, please star it :) http://code.google.com/p/googleappengine/issues/detail?id=945 Any chance someone at Google has something to say about it? Thanks, Colin On Dec 20, 5:17 am, Ben Bishop leo...@gmail.com wrote: Not sure what you mean by in case something happens - your app and its datastore is served by the same network of servers that serve other apps, so separate accounts won't help, (unless you're going against the Terms of Service, running the risk of having an account banned). One App Engine account can have 10 apps, each with its own datastore and quota. You could deploy a single app's codebase to multiple app slots, simply by changing the app name in the app.yaml for each instance. That way you could test on a production test app or one of your client apps before rolling out updates to your other client apps. You still maintain a single codebase, each client app has its own datastore, and you can control updates. On Dec 20, 2:05 am, GTako tako.ko...@gmail.com wrote: Hi, is it possible to maintain under 1 application, multiple datastores that each datastore will be as if it is different app engine account? for example: i have a web application that should serve 2 companies, A and B. I would want to open a google app engine account for the web application files. the datastores for A and B could be 2 different deployments under the same app engine account or under seperate accounts. now assume i have N companies. what should i do? the reason for seperation is that i dont want the datastores will be dependent and under same account in case soemthing happens. please advise.- Hide quoted text - - Show quoted text - --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: How much time to give for each db query in order not to occur DeadlineExceededError
Hi GAE team, how about the time for deleting? I think it would also encounter the DeadlineExceededError.. Thank you: On Dec 20, 11:52 pm, Bob bobzs...@gmail.com wrote: Too much db operations, it needs 10 seconds on my own computers to read the whole file to store in the datastore. But on the GAE, it occurs DeadlineExceededError. I gave 0.2 second for each db put(), it could work first but finally went wrong. I then gave 0.5 second and still could't solve the problem. How much time shall I give?? --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] are numeric ids of deleted entities reused?
are numeric ids of deleted entities reused? i really hope not. --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: 1 application, multiple datastores
Andy - they are essentially mutually exclusive. One suggests it should be impossible for the same piece of code to access separate datastore instances, the other suggests that this is a desirable feature. I don't see how you consider them the same - are you saying that you can't see how the cited bug is caused by multiple customers sharing the same data space? I don't understand your perspective - the difference seems utterly obvious to me. I *can* see that depending on the use case, one or the other would be good. In most cases I would say access between different customer data spaces is better modelled through an API accessible by HTTP. Perhaps you have a different use case where you have the same app deployed multiple times and do not have the customer data segregation issue, but that is not what the original poster is talking about. The original poster is *clearly* and *unambiguously* talking about avoiding bugs like the one cited, and doing so through a low level data partition. On Dec 21, 12:30 am, Andy Freeman ana...@earthlink.net wrote: Neither of the cited discussions nor your comments explain why it's different that Bill's access to separate datastore request. In fact, his request is essentially at least allows mapping a single datastore partition to the authenticated entity. There are some issues with accounting, but if your app can do its accounting in the user's datastore, you get that too. On Dec 20, 5:09 am, hawkett hawk...@gmail.com wrote: This is a required feature for a commercial SaaS/PaaS offering, and is not the same as Bill's issue in previous thread entry (Issue 06). This discussion can help you understand why - http://blogs.zdnet.com/service-oriented/?p=1236 as can bugs like this http://forum.assembla.com/forums/3/topics/256 We need it to be as close to impossible for one customer's data to be made available to another customer, without having to deploy a new instance of the application. Let's call it data segregation. A concept of 'virtual instances' would be a possible approach - so we can aggregate billing quota stats across multiple instances, and also identify individual instance billing and quota. Use Case: 1. Customer comes to my site 2. Clicks the 'Sign up now' button 3. Enters their details 4. Starts using the system You can't get a more 'core' use-case than that for a SaaS/PaaS platform. Notice there is no requirement to deploy a new version of the app for this customer. The system spawns a virtual instance of the app - or at least allows mapping a single datastore partition to the authenticated entity. You coudl extend it by allowing multiple datastores per authenticated entity and choosing the appropriate one at authentication time. The key requirement is that we can on-board a customer without manual intervention, and accurately understand a single customer's usage profile. Data corruption for one customer does not equal data corruption for another customer. This feature is in some ways the *opposite* of the feature request identified by the previous poster - we *do not* want to be able to access data in another partition - even if we tried to, and especially via a bug in our code. Here it is, please star it :) http://code.google.com/p/googleappengine/issues/detail?id=945 Any chance someone at Google has something to say about it? Thanks, Colin On Dec 20, 5:17 am, Ben Bishop leo...@gmail.com wrote: Not sure what you mean by in case something happens - your app and its datastore is served by the same network of servers that serve other apps, so separate accounts won't help, (unless you're going against the Terms of Service, running the risk of having an account banned). One App Engine account can have 10 apps, each with its own datastore and quota. You could deploy a single app's codebase to multiple app slots, simply by changing the app name in the app.yaml for each instance. That way you could test on a production test app or one of your client apps before rolling out updates to your other client apps. You still maintain a single codebase, each client app has its own datastore, and you can control updates. On Dec 20, 2:05 am, GTako tako.ko...@gmail.com wrote: Hi, is it possible to maintain under 1 application, multiple datastores that each datastore will be as if it is different app engine account? for example: i have a web application that should serve 2 companies, A and B. I would want to open a google app engine account for the web application files. the datastores for A and B could be 2 different deployments under the same app engine account or under seperate accounts. now assume i have N companies. what should i do? the reason for seperation is that i dont want the datastores will be dependent and under same account in case soemthing happens. please advise.-
[google-appengine] script handler issues
Having a hard time with wrapping my head around the script handlers. I am trying to navigate to the url http://localhost:8080/finance/worksheet and I keep getting a 404 error. Based off the directory structure and handler do you see what I am doing wrong? Thanks in advance for your help! Directory Structure: --root --finance --finworksheet.py --templates -- finance.html My app.yaml is like this: handlers: - url: /static/js static_dir: static/js - url: /static/stylesheets static_dir: static/stylesheets - url: /finance/worksheet/.* script: finance/finworksheet.py - url: /.* script: MainPage.py --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: are numeric ids of deleted entities reused?
On Dec 20, 7:09 pm, jeremy jeremy.a...@gmail.com wrote: are numeric ids of deleted entities reused? i really hope not. good question. no, they're not. you're probably already on top of this, but just for the record, ids themselves aren't unique across entities. only an entity's full path is guaranteed to be unique. ids and key names are only guaranteed to be unique among entities of the same kind that have the same parent (or that are root entities). more in http://code.google.com/appengine/docs/datastore/keysandentitygroups.html#Paths_and_Key_Uniqueness . --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Announcing: System Status Dashboard, Quota Details Page, and a Preview of Billing
We haven't yet announced information that answers your question directly. If you haven't seen it, check out the billing sneak peak we snuck in to the last blog entry: http://googleappengine.blogspot.com/2008/12/system-status-dashboard-quota-details.html#sneakpeak Of course, you'll see the whole thing when we launch the feature, which will be soon. -- Dan On Sat, Dec 20, 2008 at 5:57 PM, Thomas Johansson prenc...@gmail.comwrote: Hey, Will we be able to set a max spending limit per week and/or per month in addition to the daily limit, much like adwords? As an example, I might be comfortable spending, say, $20 on a day to survive a digg/slashdot or what have you, but not *every* day. Rather, my monthly max might be for example $100, where $20 daily with no roof would mean a lot of managing of the daily limit, or the chance of getting a lumpy $600 bill. Thanks. - Thomas On Dec 16, 7:45 pm, Marzia Niccolai ma...@google.com wrote: Hi, As many of you have already noticed, we released some Admin Console changes today, and we've also announced a System Status Dashboard ( http://code.google.com/status/appengine), and have some more details on Google App Engine's billing plans. You can read all about these announcements on our blog: http://googleappengine.blogspot.com/2008/12/system-status-dashboard-q... -Marzia --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Announcing: System Status Dashboard, Quota Details Page, and a Preview of Billing
Speaking of the billing, perhaps you can elaborate on the other quotas in place, like sending emails, urlfetch and so forth? - Thomas On Dec 21, 6:34 am, Dan Sanderson dansander...@google.com wrote: We haven't yet announced information that answers your question directly. If you haven't seen it, check out the billing sneak peak we snuck in to the last blog entry:http://googleappengine.blogspot.com/2008/12/system-status-dashboard-q... Hehe.. I'll take that as a cautious yes then. ;) Speaking of the billing, perhaps you can elaborate on the other quotas in place, like sending emails, urlfetch and so forth? Of course, you'll see the whole thing when we launch the feature, which will be soon. I've long since learned that big corporations use a vastly different definition of 'soon' than the rest of us. ;) Keep up the good work! - Thomas --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: script handler issues
Replace - url: /finance/worksheet/.* with - url: /finance/worksheet.* The URL you are trying to access doesn't have the trailing slash, but your script handler requires it. -- www.muspy.com On Dec 21, 3:14 pm, Vince vincent.zaff...@gmail.com wrote: Having a hard time with wrapping my head around the script handlers. I am trying to navigate to the urlhttp://localhost:8080/finance/worksheet and I keep getting a 404 error. Based off the directory structure and handler do you see what I am doing wrong? Thanks in advance for your help! Directory Structure: --root --finance --finworksheet.py --templates -- finance.html My app.yaml is like this: handlers: - url: /static/js static_dir: static/js - url: /static/stylesheets static_dir: static/stylesheets - url: /finance/worksheet/.* script: finance/finworksheet.py - url: /.* script: MainPage.py --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: are numeric ids of deleted entities reused?
Forgot to ask; How does the key fit into the hierarchy, compared to the key_name id? On Dec 21, 8:14 am, Thomas Johansson prenc...@gmail.com wrote: Hi ryan, Is this to be interpreted as getting the following, in order, more or less? (where the ID/Key is in square brackets) /Image[42] /Image[127841] /Thread[10]/Post[42] /Thread[10]/Post[127841] E.g. the ID is ever increasing, but only for the current fully qualified path? Can we ever experience inserting a record that will have a lower ID than the previous? Thanks, Thomas On Dec 21, 6:13 am, ryan ryanb+appeng...@google.com wrote: On Dec 20, 7:09 pm, jeremy jeremy.a...@gmail.com wrote: are numeric ids of deleted entities reused? i really hope not. good question. no, they're not. you're probably already on top of this, but just for the record, ids themselves aren't unique across entities. only an entity's full path is guaranteed to be unique. ids and key names are only guaranteed to be unique among entities of the same kind that have the same parent (or that are root entities). more inhttp://code.google.com/appengine/docs/datastore/keysandentitygroups.h... . --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: are numeric ids of deleted entities reused?
Can we ever experience inserting a record that will have a lower ID than the previous? You can, at least that's what I'm seeing in my app. As far as I understand, the IDs are pre-allocated in batches, and if your app actually runs on different boxes, they will use IDs from different batches. --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
