Re: broadcast address of a network interface
Re: broadcast address of a network interface
- Subject: Re: broadcast address of a network interface
- From: Joel Reymont <email@hidden>
- Date: Mon, 9 Feb 2009 20:39:57 +0000
On Feb 9, 2009, at 8:21 PM, Hostile Fork wrote:
http://en.wikipedia.org/wiki/IP_Multicast#Wireless_.28802.11.29_Considerations
With transmissions every 100-200-300ms, I think I'll skip multicast
for now.
If (and it's a big if!) someone buys my app and tries it out, they are
unlikely to go about adjusting beacon intervals. They will just delete
the app and give me a bad rating.
Further, in this walkie-talkie scenario, why open N TCP connections
and not send N UDP packet streams? I was under the impression that
broadcast-type applications like this which could tolerate the
occasional lost packet *should* be done with UDP.
This is the way I'm leaning, simply because it's much easier to track
and use 2 streams (in/out) in the app that 2 streams per client.
Intuitively, I perceive that it will be much faster too and much less
work for the device.
On the other hand, this may just be premature optimization. Why not
use TCP if it works? Then again, Bonjour does not leave the LAN and
there shouldn't be much packet loss on a LAN with UDP.
It sounds like two implementations will be required and results will
need to be published! Blog below.
---
http://tinyco.de
--- Mac & iPhone
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden