Graeme, I have the same question. I see that in ConectivityService there's a setNetworkPreference(TYPE_WIFE or TYPE_MOBILE), which invokes enforcePreference, which checks if the current preference is the new, and if not, and it is active, it tears it down. This leads me to believe that there is only one interface visible to the IP stack at at time. I can see how this might make routing simpler, but what confuses me is this:
I am not seeing anywhere in the code where, for instance, and MMS message would cause the WIFI interface, it it is active, to be torn down and the MOBILE activated. It is possible that this is done through the transaction interface, and I'm starting to lean in that direction, but does anybody know if this is true? Here's the question (assuming MMS must be routed over the Mobile network): If WIFI is the current preferred network, and active, will an MMS transaction cause the WIFI interface to be torn down and the MOBILE to be activated? Thanks, Dave On Sep 25, 8:24 am, Graeme <[EMAIL PROTECTED]> wrote: > Hi > > The android.net.ConnectivityManager has a member function > requestRouteToHost(int networkType, int hostAddress) to ensure that a > route is maintained to deliver traffic to a specified host via a > specifiednetworkinterface(TYPE_WIFI or TYPE_MOBILE). > > Now does this mean that Android supports multi-homing, that is being > connected to a cellular datanetworkand a WiFi-basednetworkat he > same time ? > > Thanks > Graeme --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
