Re: [rtcweb] Current state of signaling discussion

[Cullen Jennings <[e-mail]>]

On Oct 18, 2011, at 14:05 , Hadriel Kaplan wrote:

> BUT, for an actual session protocol to work for even a gaming app, you need to do the following:
> 1) determine a target for the ROAP message (ie, who's this OFFER going to in the end?)
> 2) define how that target identity is conveyed (ie, how does the web server know which browser to give this ROAP OFFER to?)
> 3) define a source identity model, possibly with authentication (ie, who are you?)
> 4) define how the source identity is conveyed (ie, how does the server/far-end-browser know who's calling?)
> 5) define a end-of-session indication
> 6) define a keep-alive mechanism, for when the far end goes away silently and (5) doesn't apply

I've thought a bunch about this - In addition to those, I think we need a way to cache state, sort of like cookie or something. That gets passed back at the right time. That type of thing makes it much easier for the web-service to keep track of things.