Hi Enrico, Ravi, On Wednesday, July 25, 2012, Ravi nandiraju wrote:
> > > ________________________________________ > From: Enrico Marocco [[email protected] <javascript:;>] > Sent: Wednesday, July 25, 2012 1:13 PM > To: Ravi nandiraju > Cc: [email protected] <javascript:;> > Subject: Re: [alto] WebSocket-based notifications > > On 7/25/12 7:47 AM, Ravi nandiraju wrote: > > I don't envisage ALTO clients like home devices using the > > subscription mechanism because, for a home device client it is easier > > to query the ALTO server for a changed map information rather than > > going for a subscription. > > > Just to be clear, here by "home device" you actually mean "user > devices", i.e. any laptop, desktop, smartphone and whatnot that may for > example run in a home network. > > [Ravi] Yes. What I meant by "home device" are the devices which are used > by end users as P2P clients and which could potentially use ALTO as clients. > > > IMO, this subscription mechanism would be useful for infrastructure > > cases like gateway devices, CDN, inter-DC etc where the problem of > > reachability is not so complex as in the case of peer to peer. > > And useless in any environments where global reachability cannot be > taken for granted. Agreed. > > [Ravi] Basically what I meant was, we don't need to consider the case of > "user devices" for subscription/notification because for them it is easier > to query the information based on need rather than subscribing. I am not > very clear if reachability is really a concern in the use case for ALTO > subscription/notification. Interesting perspective to focus on the desgn scenario. Ignoring reachability for a moment and considering only overhead, since the number of user devices will be large, the design of user-device-pull vs that of server-push-to-user-device will be a trade off between bandwidth/throughput vs server connection/open connection overheads. In this setting, I agree that user-device-pull appears to be more preferred. On the other hand, if we consider alto as a mechanism for network to update info to user devices (e.g., end point properties, in a general context; i am even thinking of network notify user device its last mile usage/quota/load properties), then server-push-to-user-device can have benefits, such as low latency. What do you think or this is too pushed? Thanks! Richard > > -- > Ciao, > Enrico > _______________________________________________ > alto mailing list > [email protected] <javascript:;> > https://www.ietf.org/mailman/listinfo/alto >
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
