Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!munnari.oz.au!mel.dit.csiro.au!yarra!melba.bby.oz.au!gnb From: gnb@bby.oz.au (Gregory N. Bond) Newsgroups: comp.protocols.tcp-ip Subject: Reliable Broadcasts? (was Re: Reliable Datagram ??? Protocols) Message-ID: Date: 23 Oct 90 03:31:32 GMT References: <9010221418.AA03839@ftp.com> Sender: news@melba.bby.oz.au Organization: Burdett, Buckeridge and Young Ltd. Lines: 23 In-Reply-To: jbvb@FTP.COM's message of 22 Oct 90 14:18:35 GMT Well, on a similar note.... I understand James' and Jon's arguments. Reliable datagrams are best implemented with TCP and a "write(len); write(data);" layer. I am looking for something a little different. Consider a net with a server and many (say, 100) workstations, and a data feed that goes to each workstation. At the moment, I have to open 100 TCP streams, and so each packet of data generates 200 TCP packets, all more-or-less identical. What would be nice would be to broadcast the packet to the local net, and have the clients request missed packets, thus implementing a sort of reliable broadcast. I would be happy for some sort of overhead for the reliability (e.g. server broadcasts empty packets with the highest serial number once every 10 seconds), but before I re-invent wheels, has someone done something like this? Greg. -- Gregory Bond, Burdett Buckeridge & Young Ltd, Melbourne, Australia Internet: gnb@melba.bby.oz.au non-MX: gnb%melba.bby.oz@uunet.uu.net Uucp: {uunet,pyramid,ubc-cs,ukc,mcvax,prlb2,nttlab...}!munnari!melba.bby.oz!gnb