Or to put it another way, the current method is to use a make a server somewhere on the internet (or perhaps wifi intranet) to catalog and function as an intermediary between the phones.
In the future or maybe now with low-level hacking, ad-hoc wifi or something bluetooth based could become an option. On Oct 5, 4:09 pm, "Roman ( T-Mobile USA)" <roman.baumgaert...@t- mobile.com> wrote: > If you want to communicate within a wireless LAN (using > infrastructure mode on Wifi) you can come up with your own discovery > protocol. > > If you want to communicate outside your locale network, you might want > to use some cloud service which can help with client discovery. > > Another option might be Wifi Adhoc. Current Android SDK has no support > for Wifi Adhoc, but you can get it running on platform level (or wait > till it's supported). > > -- > Roman Baumgaertner > Sr. SW Engineer-OSDC > ·T· · ·Mobile· stick together > The views, opinions and statements in this email are those of the > author solely in their individual capacity, and do not necessarily > represent those of T-Mobile USA, Inc. > > On Oct 2, 4:51 pm, Jerome White <jer...@cs.caltech.edu> wrote: > > > I'd like to build an application in which there are several Android > > devices that communicate amongst themselves. What is the best way to > > do this? Wi-Fi seems like a good option, in that you can discover your > > neighbors and don't need any hard coded identifiers (such a phone > > number), but I'm not sure. What is the standard practice? Thanks > > > jerome --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to android-beginners-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
