Ticket #146 (closed Tasks: fixed)
Implement automatic network interface selection
| Reported by: | octo | Owned by: | octo |
|---|---|---|---|
| Priority: | minor | Milestone: | 2.0 |
| Component: | LogicMail | Version: | None |
| Keywords: | Cc: | jkamens@… | |
| Blocked By: | Blocking: |
Description
"Kamens, Jonathan" <jkamens@…> wrote:
It would be great if I could tell LogicMail to try to connect via WiFi and then fall back on connecting through the phone network if WiFi fails.
Even better would be if LogicMail checked whether WiFi was enabled and only tried if it was.
Even better would be if LogicMail checked whether there was an active WiFi connection and only tried to connedt via WiFi if there was.
Basically, I'd like LogicMail to be smart enough to use WiFi when it's available and working and not use it otherwise.
Intelligent network detection is one of the features on the TO-DO list for 2.0. There are plenty of potentially tricky implementation details of course. Probably the hardest one is cases where you are connected via Wi-Fi, but there is a firewall blocking some E-Mail protocol from getting through. I've found this to be an annoyingly common occurrence.
This won't be going into 1.1, though, since I'm still keeping my "no signed APIs" policy for that branch. Of course, as you might guess, the network status APIs all require signed code. (for more detail on what that issue is, see the faq.
Change History
comment:1 Changed 2 years ago by octo
- Status changed from new to assigned
- Owner set to octo
- Type changed from Feature Requests to Tasks
- Summary changed from Add intelligent selection of Wi-Fi networking to Implement automatic network interface selection
comment:2 Changed 2 years ago by octo
- Status changed from assigned to accepted
Changeset [608] has the draft implementation of all the new configuration changes and the pre-5.0 logic. It will need extensive on-device testing, since it is impossible to test such things in the simulator.
comment:4 Changed 2 years ago by octo
This will take some time to work all the kinks out of. WiFi detection appears broken at the moment on devices w/o SIM cards. A lot more testing/experimenting is required to get this all working correctly. On the bright side, WAP 2.0 appears to be working.
comment:5 Changed 2 years ago by octo
[613] fixes the above issue and [614] adds support for the new 5.0 network connection API, which hopefully completes this task for now. Its still possible that there are kinks to work out, and those will be treated as separate bugs.
Automatic connection management (polling, closing, reopening, etc.) will be done as an entirely separate development task.
This feature just got a lot more interesting, since BlackBerry OS 5.0 provides a brand-new API for things just like this. Most likely I'll wind up with multiple implementations depending on the target OS version. Regardless, it is definitely a must-have for 2.0.