You could reuse a token for a particular user within the token's two hour window. You'd need some kind of method for checking whether or not it's still in use in another tab (perhaps periodic check ins via ajax). If you can be confident that a user has closed a tab, you could reuse the token from that tab for the duration of that token's 2 hour window.
This definitely seems less than ideal. It seems to me that appengine's quota should deal with how many connections you can have at a given time, rather than how many times you can create channel tokens. But given the way it's currently structured, I think figuring out how to reuse channel tokens will be necessary for apps with large user bases. On Dec 3, 6:48 pm, supercobra <[email protected]> wrote: > We definitively need more than 100K. Each time a user open close his / > her browsing session it is counted as 1 channel creation. I open and > leave Gmail, and open new windows at least 50 / 100 times a day. So if > 1000 users use an app like I use Gmail then it makes about 100K > channel api creation / day for them. > > Based on this calculation, I think 100 channel api creations / day is > a good starting number. So if my app has 30,000 users I'll need 3m > slots... > > I think the challenge for Google is the long running - for nothing - > connection for example like when you leave your browser open and go to > lunch or home for the evening.... > > -- [email protected] > > Co-author of App Engine Java and GWT > Development:http://bit.ly/hdTHyBhttp://supercobrablogger.blogspot.com/ > > > > > > > > On Fri, Dec 3, 2010 at 3:22 PM, Rafael Sierra <[email protected]> wrote: > > On Fri, Dec 3, 2010 at 7:15 PM, Geoffrey Spear <[email protected]> wrote: > > >> On Dec 3, 12:57 pm, Peter Petrov <[email protected]> wrote: > >>> For billing-enabled apps the quota is 95040 channels created per day. This > >>> is still extremely low, I completely agree. > > >>> If I remember correctly, yesterday after the 1.4.0 release this quota was > >>> considerably higher (about 10 times). Probably they are having capacity > >>> problems with the GAE / GTalk infrastructure. Some official explanation > >>> would be nice, though. > > >> The Channel API isn't even listed on the Quotas page yet ( > >>http://code.google.com/appengine/docs/quotas.html), but it's not > >> unreasonable to believe there will be an option to request an increase > >> like there is for the other fixed quotas that are listed there. > > > It is for me: > > > Channel > > Channel API Calls 0% 31,574 of 91,995,495 Okay > > Channels Created 2% 1,815 of 95,040 Okay > > Channel Data Sent 0% 0.00 of 2,088.13 GBytes > > >> -- > >> 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 > >> athttp://groups.google.com/group/google-appengine?hl=en. > > > -- > > Rafael Sierra > >http://blog.rafaelsdm.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 [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/google-appengine?hl=en. -- 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.
