But as I understand, client ids don't have to be a one-to-one mapping to users. If you need to be able to handle multiple tabs/windows, you would need a different client id for each tab, regardless of whether or not you intend to reuse tokens. I'm envisioning something like this:
Client A connects: Generate token on client id 'client_a_1', record in datastore. Client A connects again: Generate token on client id 'client_a_2', record in datastore. First window disconnects or times out: Mark token associated with 'client_a_1' as unused. Client A connects: Send token associated with 'client_a_1' Then you have different channels for different tabs (so everything should work as expected), but you don't have to use a channel creation if a user has a token that is not in use. Is there a flaw in this plan that I'm missing, or would this work as I expect? -- 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.
