Re: audio/video again
At 05:53 PM 8/5/96 -0700, Michael Dillon wrote:
Maybe we could get an RFC that requires screensaver type applications to have a standalone mode that works with stored data and require user overrides in order to initiate video or other data feeds. Maybe it could also require that video and data feeds automatically shut down if there is no user interaction within a specified time period. Kind of a higher level view of the smae kind of timing specs that make TCP work.
Hey, don't mess with my Pointcast! ;-) Sorry to name specific products here (lots of folks specifically point out cisco, so what the hell), but in the specific case of Pointcast, there *is* a knob which controls the time-frame between updates. This is, in my opinion, the Right Thing to do. Once they get the compression stuff working and make it available, it will help lessen the impact of thousands of these clients clogging the network getting update data. In any event, I like getting my stock quotes if I'm away from my machine for a few hours. Sure, there are ways to make it more efficiently (such as geographically dispersed servers, compression, et al), but I don't believe this is an example of a misbehaving application. Perhaps an FYI RFC on application behavior is not such a Bad Thing, but it would certainly be a controversial document. - paul
On Mon, 5 Aug 1996, Paul Ferguson wrote:
Sorry to name specific products here (lots of folks specifically point out cisco, so what the hell), but in the specific case of Pointcast, there *is* a knob which controls the time-frame between updates. This is, in my opinion, the Right Thing to do.
How would you feel if Pointcast slowly backed off and increased the time period between updates, but at the touch of a key or movement of the mouse it would go back to the "knob" setting? Obviously a low volume data feed like Pointcast may not be that big a load on the net but the heuristics (which do involve human factors) could probably be applied to a lot of other things like video feeds that will be bigger bandwidth consumers. Of course, maybe we could have some sort of streaming feed discovery protocol whereby a server can detect that multiple clients are receiving the same stream and ask them to negotiate with each other and appoint a master client that relays the feed locally to the other clients.
Perhaps an FYI RFC on application behavior is not such a Bad Thing, but it would certainly be a controversial document.
This can be a good thing because it gets the issue noticed and some of the people on the sidelines go off and do real work that can result in resolving the real problems. Michael Dillon - ISP & Internet Consulting Memra Software Inc. - Fax: +1-604-546-3049 http://www.memra.com - E-mail: michael@memra.com
participants (2)
-
Michael Dillon -
Paul Ferguson