[Opentnl-general] Re: Quickest Delivery Data
Brought to you by:
mark_frohnmayer,
s_alanet
From: Ben G. <be...@ga...> - 2005-02-09 23:03:13
|
Hey Kevin, Mark is likely to be able to give a fuller answer, but here's my understanding - the quickest delivery is for stuff like movement data or current position, not for NetEvents, which are more discrete chunks of information. So if you look at the zap demo app, you'll see that quickest delivery is implemented for the control object (for instance) by simply writing the data out for each packet, using a subclass of GhostConnection. Quickest delivery isn't very useful for NetEvents because in theory they store their data as part of each NetEvent instance, ie, it's not dynamic data. Naturally, you could extend the NetEvent semantics to include a QuickestDelivery type if you wanted, but I can't think of many good reasons off the top of my head. Not to say I'm not curious to hear one! :) Hope this helps. Regards, Ben Garney Torque Technology Director Kevin Deus wrote: > The "Fundamentals" page of the TNL documentation mentions "Quickest >Delivery data" as a strategy for dealing with packet loss. From working >with the library, I can see that the groundblocks are in place for sending >this kind of data, but is there a full implementation of it anywhere, like >there is for Current State data, Guaranteed Ordered data, and so on? > > Ideally, I'm hoping for something like another enum value for >NetEvent::GuaranteeType: something like QuickestDelivery. ...but maybe I'm >looking in the wrong place. > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >_______________________________________________ >Opentnl-general mailing list >Ope...@li... >https://lists.sourceforge.net/lists/listinfo/opentnl-general > > > > |