> > > > Another idea, you get 9 hours of backend free a day too. Could you shunt > the 'users' to actully be done via your backend. Leaving the single frontend > instance to serve kiosk traffic? > > > If I can, then I clearly don't understand what a backend is. > > Can you elaborate on this idea? > > Its another type of instance :)
http://code.google.com/appengine/docs/python/backends/overview.html ". Dynamic backends come into existence when they receive a request, and are turned down when idle; they are ideal for work that is intermittent or driven by user activity." "Backends do not automatically scale in response to request volume. Instead, you specify the number of instances of each backend" http://code.google.com/appengine/docs/python/config/backends.html "An integer between 1 and 20 indicating the number of instances to assign to the given backend. Defaults to 1 if unspecified." Can make a backend public http://code.google.com/appengine/docs/python/backends/overview.html#Public_and_Private_Backends Can queue requests http://code.google.com/appengine/docs/python/config/backends.html#Request_Handling ... so based on all that information. the frontend instance, could upon getting a visitor, spin up a backend (unless there already is one) and redirect the user to it. A backend - will *strictly* adhere to the 1 instance limit. The dynamic backend will then be torn down when not used for a few minutes. ... so providing you get under 9 hours of user interaction in total on the site, it could use a free backend. (But milling is by the hour, so cant be lots of split in lots of bits over the day :( ) (still requires that your kiosk requests and the occasiaonl redirect, can exist on one instance. ) -- 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.
