On Sat, 29 Dec 2001, Scott C. Best wrote: > Paul: > > Heya. Notso left field, really. I've used ipfwd to > forward IPSec packets (protocol 50 and 51) to my NAT'd LAN's > broadcast address...and IPSec clients on that LAN can handle > it. > Of course...IPSec has some sense of "state" of a > connection beyond just the packets. Webservers don't. I wonder > what would happen with some game servers, or VNC. Hmmm...
Webservers have a very clear "sense of 'state'" in their connections beyond just the packets. They use TCP, which maintains a "pipe" long enough to support a request and reply between the client and the server. The "statelessness" attributed to webservers has to do with the fact that these connections are generally very short-lived... under http 1.0, only a single request/reply is supported before the connection is dropped. Multicasting is useful for "now" data... radio broadcasts, for example, where if you don't get the sound from a few seconds ago, oh well, because you won't be able to catch up to the sound corresponding to "now" if you try to listen to re-transmissions of packets sent "then". Large file transfers cannot afford to omit retransmissions, and some amount of delay is worth the delay involved in making sure the file gets through intact. One level of difficulty is variable reliability of transmissions. Keeping track of the fact that after transmitting 300 packets, destination A needs a retransmission of packet 293, but destination B needs packet 297, and destination C got it all so far, is outside the scope of normal TCP connections. They only work on a one-to-one basis. Another level of difficulty is the fact that the application level protocols are typically designed for point-to-point communication... the communication initiator does not expect to hear several voices answer when it says "Hello". Therefore I think Charles' suggestion to have an application-level "repeater" would be the only way to construct this data flow. > > -Scott > > > > Maybe this is way out in left field, but could this be a potential > > application for multicasting? > > > > paul > > > _______________________________________________ > Leaf-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user > --------------------------------------------------------------------------- Jeff Newmiller The ..... ..... Go Live... DCN:<[EMAIL PROTECTED]> Basics: ##.#. ##.#. Live Go... Live: OO#.. Dead: OO#.. Playing Research Engineer (Solar/Batteries O.O#. #.O#. with /Software/Embedded Controllers) .OO#. .OO#. rocks...2k --------------------------------------------------------------------------- _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
