Multicast does this for you automatically, however, Bluetooth currently does not support multicast like IP. It is PTP.
see this link: http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&ved=0CF4QFjAB&url=http%3A%2F%2Fwireless.cs.tku.edu.tw%2F~cychang%2FTMCP.pdf&ei=Z366T63_MLGUmQXHj4GzCQ&usg=AFQjCNGw-2ARQ1I-FXu30Qtpxgwsh3Wb9w&sig2=vedcvR89NgXqjsJV9Fz1vQ On Mon, May 21, 2012 at 10:23 AM, Kristopher Micinski < [email protected]> wrote: > That would be the same as any other message queue adapted to sit on > top of a different socket layer, however, I believe... > > kris > > On Mon, May 21, 2012 at 1:11 PM, mike digioia <[email protected]> wrote: > > Oh sorry I just stated what I believe is the current packet size > linitation > > of BT as 950. > > > > Yes you are correct about the limitations on any one device today. > However, > > the CCNX will handle the networking of devices as it does today over IP. > > Nothing is being changed inside the CCND except to handle as additional > BT > > socket type. > > > > > > On Mon, May 21, 2012 at 9:56 AM, Kristopher Micinski > > <[email protected]> wrote: > >> > >> Right, that's what I said... But I also said that I doubt that for a > >> real live device, if any one can have more than two open connections > >> at a time, I'd be surprised, please tell if so! And, if you're > >> talking to 950 nodes where the average degree is two for each node... > >> That's gonna be pretty harsh ;-) > >> > >> kris > >> > >> On Mon, May 21, 2012 at 12:53 PM, mike digioia <[email protected]> > wrote: > >> > You can do this with a multicast based Openfire system! This uses IP. > >> > Bluetooth as the transport using sockets is still under study, since I > >> > am > >> > just attempting to get the first case to work with only one chat > between > >> > two > >> > phones. Since this uses Content Centric networking, it can be extended > >> > to > >> > handle many nodes by extending bluetooth headers and doing packet > >> > fragmentation (BT max is 950) to handle large packets. > >> > > >> > On Sun, May 20, 2012 at 10:01 AM, Kristopher Micinski > >> > <[email protected]> wrote: > >> >> > >> >> You basically, can't do it for Bluetooth, with more than two / three > >> >> (max usually) nodes. > >> >> > >> >> You can look into wifi direct. > >> >> > >> >> You can also put a p2p overlay on top of a standard java socket. But > >> >> that makes this no more interesting than any desktop java app. I.e., > >> >> there is absolutely nothing that makes it Android specific. > >> >> > >> >> http://www.zeromq.org/build:android > >> >> > >> >> There's a 0MQ build on Android, but it's using the NDK, and I haven't > >> >> seen Java bindings, so it's probably going to a real pain to use. > >> >> (Though in real apps, a message queue like 0mq would be a real > >> >> lifesaver, since you're basically going to emulate that anyway!) > >> >> > >> >> kris > >> >> > >> >> On Sun, May 20, 2012 at 12:41 PM, sudheesh ap <[email protected] > > > >> >> wrote: > >> >> > Yes, it's for a class project. The aim is to make a p2p > overlay > >> >> > network > >> >> > in android platform to support p2p android applications such as > >> >> > multiplayer > >> >> > games.I was asking about the possibility to make it over the > >> >> > bluetooth/wifi > >> >> > connection. Waiting for your valuable suggestions. > >> >> > > >> >> > Regards, > >> >> > sap > >> >> > > >> >> > -- > >> >> > You received this message because you are subscribed to the Google > >> >> > Groups "Android Developers" group. > >> >> > To post to this group, send email to > >> >> > [email protected] > >> >> > To unsubscribe from this group, send email to > >> >> > [email protected] > >> >> > For more options, visit this group at > >> >> > http://groups.google.com/group/android-developers?hl=en > >> >> > >> >> -- > >> >> You received this message because you are subscribed to the Google > >> >> Groups "Android Developers" group. > >> >> To post to this group, send email to > >> >> [email protected] > >> >> To unsubscribe from this group, send email to > >> >> [email protected] > >> >> For more options, visit this group at > >> >> http://groups.google.com/group/android-developers?hl=en > >> > > >> > > >> > -- > >> > You received this message because you are subscribed to the Google > >> > Groups "Android Developers" group. > >> > To post to this group, send email to > [email protected] > >> > To unsubscribe from this group, send email to > >> > [email protected] > >> > For more options, visit this group at > >> > http://groups.google.com/group/android-developers?hl=en > >> > >> -- > >> You received this message because you are subscribed to the Google > >> Groups "Android Developers" group. > >> To post to this group, send email to > [email protected] > >> To unsubscribe from this group, send email to > >> [email protected] > >> For more options, visit this group at > >> http://groups.google.com/group/android-developers?hl=en > > > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to [email protected] > > To unsubscribe from this group, send email to > > [email protected] > > For more options, visit this group at > > http://groups.google.com/group/android-developers?hl=en > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
