Mark,
I think the loss of XMPP-like capability is pretty big. Mike Cleron in the youtube Androidology said that he thinks the compelling apps (mashups) include that capability. I think it really replaces the server infrastructure. If you build a server infrastructure now, then soon your app won't need it. How does that work? :) Well, you can't really build the app properly yet. ..But it's good that it will be more built into the system, attached to android and not just to a Google address. - Juan T. On Oct 5, 3:52 pm, Mark Murphy <[EMAIL PROTECTED]> wrote: > whitehexagon wrote: > > I'm really struggling to find information on if it's possible to get > > two android handsets talking to each other without an intermediate > > server. In theory this should be possible via wireless or more likely > > BlueTooth. But both API's seem crippled to prevent this, or am I > > missing something? > > It has been stated that the Bluetooth APIs were taken out due to lack of > time to get the API stabilized in time: > > http://android-developers.blogspot.com/2008/08/some-information-on-ap... > > Peer-to-peer Internet communication should be as possible on Android as > it is on any platform -- difficult with absolutely zero server > assistance, but not too tough if you can at least use a server for > obtaining the IP address of the peer(s) to communicate with. Of course, > there are issues of firewalls, NAT traversal, mobile carrier terms of > service, and security to deal with, none of which are trivial. > > > I find it hard to believe android would be > > > launched without some kind of phone to phone communication support? > > If the Android core team committed to doing everything everyone wanted > before 1.0, we'd never have any Android devices, because they would > never be done. You want built-in P2P. Some other guy wants built-in > infrared. Still others want A2DP profiles. Yet others want all those API > features hackbod gets to say aren't available in 1.0. And so on. The > Android core team had to draw a line *somewhere*. > > The good news is that, once Android 1.0 is released as open source, > there will hopefully be a means for public contributions, meaning you'll > be able to help add those things you feel are needed. > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > _The Busy Coder's Guide to Android Development_ Version 1.3 Published! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
