Thank you for your reply Moishe. It's good to know that the "create" quote is on it's way out.
I'm not sure that charging by "minutes requested" apposed to "minutes consumed" actually solves the problem, thought. Instead of reusing one "long lived channel" developers will be forced to create many "short lived channels", unless there's some financial deterrent in doing so. Also, charging by "minutes requested" seems contrary to App Engine philosophy of pay for the resources you use, and more like a cell phone plan, which relies on people purchasing based on least surprise. I don't see the later translating well in this environment, however. I can't imagine a developer paying for excess minutes, just to prevent a disconnect by app engine, when they would have to prepare for this anyways. In my mind the ideal solution would better mirror web sockets. Where I don't need to decide a head of time how long a user might decide to say on my site. If there is an increased cost associated with the channel creation, on your end, I personally wouldn't be apposed to a minimum minute expiration ( much like the 15min instance minimum ). Thanks for listening, Kyle -- 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.
