04-07-2009 03:23 PM - last edited on 04-08-2009 06:21 AM
This post available for the things I've forgotten about.....
Other extremely useful Threads
On some devices, a voice call will interrupt a connection. This Thread discusses the implications for a Phone Listener.
http://supportforums.blackberry.com/rim/board/mess
Edit: Decided this was a good place to add references to other extremely useful networking related Threads.
04-08-2009 03:26 AM
04-08-2009 03:45 AM
As always Excellent work.
All Network Info in one thread.
This should be a Sticky thread.
04-08-2009 03:58 AM
Should be a sticky thread.. Nice work peter.. Excellent!
Thanks!
04-08-2009 07:00 AM
http://supportforums.blackberry.com/rim/board/mess
HyperText Transfer Protocol (HTTP), which is the primary protocol of the World Wide Web, has a special method known as CONNECT. This method is used by a user device to instruct a proxy server to establish a connection with a remote server so that handshaking between the user device and the remote server can take place.
Thanks!
04-08-2009 09:31 AM
04-08-2009 01:18 PM
Great info as usual Peter.
You said this:
"Aside: Note in some (typically older) devices, the device itself would attempt to determine the best connection method, if you specified nothing at all. In fact I have some devices who will only connect correctly if you do this. However these are the exceptions rather than the rules."
How old is "older"? The application I'm working on currently does nothing to append parameters to URLs, but I've found it to work for T-Mobile 8320 (non-corporate, providing the APN info is typed in), ATT 8320 (both corporate and not), 8820 ATT (corporate) and Pearl 8100 (T-Mobile corporate).
Would 8900, Bold, Pearl Flip or Storm require the URL parameters?
04-08-2009 04:37 PM
Good question. I knew that statement would get me in trouble.
The current version of the standard KB article (DB-00396 - What Is - Different ways to make an HTTP or socket connection) says this:
"By default, all BlackBerry smartphone models, except the BlackBerry® 6500 Series and the BlackBerry® 7500 Series, use BlackBerry MDS by default"
From memory, in the previous version of this article, there used to be more exceptions, especially devices that ran on networks that I had never heard of (for example IDEN?). But more importantly, there were comments about devices that would attempt to determine their best route. These comments have been removed, I presume because they were confusing, and with CoveragineInfo, in theory, the application program can select the correct method. But as you have found out, in some cases, it appears the logic is still there.
I think I'm going to ask for input from Rim on this one.
04-09-2009 10:06 AM
If you don't specify any parameters in your connection, BlackBerry handhelds will first try to connect using the MDS Connection Service of a BlackBerry Enterprise Server, if the user has been configured on a BES. If they are not on a BES, it will attempt to make a direct TCP connection.
The exception to this rule are BlackBerry handhelds that run on the iDEN network. They try to connection in the reverse order (direct TCP first, then BES). This would be the BlackBerry 6500 series, 7500 series and the BlackBerry 8350i. I'll update the KB to add this new model.
04-10-2009 11:49 AM - last edited on 04-10-2009 11:56 AM