On 7/24/12 11:57 AM, Ravi nandiraju wrote: > Yes. Websockets will be useful for cases where there are frequent > notifications (like server load etc). This is only one use case for > subscription/notification. IMO, we should define a generic framework > for subscription/notification which includes support for things like > multiple event subscription and does'nt have the overhead of > persistent connections when the clients are not interested to keep > them.
This is actually something the authors would like to get feedback about, i.e. whether people prefer to have one connection per resource, or some sort of subscription protocol running for multiple resources on a single connection. The draft at this point suggests the former approach, basically for simplicity. > Regarding the server creating a connection to the client, the client > explicitly advertises its contact address for the server to connect > to. The reachability problem should be solved by the client. I cannot think of any way for the client to solve the reachability problem that is less demanding in terms of resources than a client-initiated connection. Can you suggest one that works with today's firewalls, access gateways and carrier NATs? -- Ciao, Enrico
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
