| To: | Terje Eggestad <terje.eggestad@xxxxxxxxx> |
|---|---|
| Subject: | Re: anyone ever done multicast AF_UNIX sockets? |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | Mon, 3 Mar 2003 21:38:17 -0500 (EST) |
| Cc: | Chris Friesen <cfriesen@xxxxxxxxxxxxxxxxxx>, linux-kernel <linux-kernel@xxxxxxxxxxxxxxx>, "" <netdev@xxxxxxxxxxx>, "" <linux-net@xxxxxxxxxxxxxxx>, "" <davem@xxxxxxxxxx> |
| In-reply-to: | <1046734165.27924.263.camel@eggis1> |
| References: | <3E5E7081.6020704@xxxxxxxxxxxxxxxxxx> <1046695876.7731.78.camel@xxxxxxxxxxxx .scali.no> <3E638C51.2000904@xxxxxxxxxxxxxxxxxx> <1046720360.28127.209.camel@eggis1> <3E63D73A.2000402@xxxxxxxxxxxxxxxxxx> <1046734165.27924.263.camel@eggis1> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
Hi Terje, On Mon, 4 Mar 2003, Terje Eggestad wrote: > How do you design a protocol that uses multicast to send a request to do > work? > > All uses I can think of right now of multicast/broadcast is: > * Discovery, like in NIS. > * Announcements like in OSPF. > * update like in NTP broadcast > I know we are digressing away from main discussion ... The concept of reliable multicast is known to be useful. Look at(for some sample apps): http://www.ietf.org/html.charters/rmt-charter.html But we are talking about a distributed system in that context. Agreed, reliability and multicast do not always make sense. cheers, jamal |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: anyone ever done multicast AF_UNIX sockets?, Terje Eggestad |
|---|---|
| Next by Date: | [PATCH][bonding] division by zero bug, Shmulik Hen |
| Previous by Thread: | Re: anyone ever done multicast AF_UNIX sockets?, Terje Eggestad |
| Next by Thread: | Re: anyone ever done multicast AF_UNIX sockets?, Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |