[kberry]

Does anyone have a clue what some of these undocumented
parameters are that the RIM BlackBerry browser is using when
it goes to make its calls to 'Connector.open()'??


* BlackBerry Browser - Using BlackBerry Internet Service (BIS)

Here are the exact parameters used by the BlackBerry browser
for its Connector.open() call when it is using the BlackBerry Internet
Service (BIS) on an BB 8830 purchased from ATT....

http//www.somewhere.com/;DeviceSide=false;ConnectionSetup=delayed;UsePipe= true;ConnectionUID=GPMDSNA01;ConnectionTimeout=120 000;EncryptRequired=true

Here are the exact parameters used by the BlackBerry browser
for its Connector.open() call when it is using the BlackBerry Internet
Service (BIS) on an BB 8830 purchased from VERIZON...

NOTE: Identical to the parms used for the ATT BIS call above with
the following 2 exceptions...

VERIZON parms do not include 'UsePipe=true'
VERIZON parms add a parameter called 'SpecificUID=S64037865'

http//www.somewhere.com/;DeviceSide=false;ConnectionSetup=delayed;Connecti onUID=GPMDSNA01;SpecificUID=S64037865;ConnectionTi meout=120000;EncryptRequired=true


* BlackBerry Browser - Using WAP Gateway...

Here are the exact parameters used by the BlackBerry browser
for its Connector.open() call when it's NOT using BIS or BES and is
making a request via a WAP Gateway on a BB 8830 purchased from ATT...

http//www.somewhere.com/;retrynocontext=true;DeviceSide=true;ConnectionSet up=delayed;ConnectionUID=WAP2 trans

Here are the exact parameters used by the BlackBerry browser
for its Connector.open() call when it's NOT using BIS or BES and is
making a request via a WAP Gateway on a BB 8830 purchased from VERIZON...

NOTE: IDENTICAL to parms used by ATT BlackBerry device.

http//www.somewhere.com/;retrynocontext=true;DeviceSide=true;ConnectionSet up=delayed;ConnectionUID=WAP2 trans


* THE PARAMETERS ???

Some of these are documented, some are not.
It's the undocumented ones that I am curious about...

* DeviceSide=false

Basically... if you want the request to use BIS or BES then
it's got to be "DeviceSide=false". If you want the request to
use the WAP Gateway or sockets: protocol then it has to
be "DeviceSide=true".

* ConnectionSetup=delayed

?? Undocumented ?? What does this really mean?

* UsePipe=true

?? Undocumented ?? - Only appears when ATT device is using BIS?

* ConnectionUID=GPMDSNA01

Refers to a Service Book UID from which specific Connection
information is retrieved. GPMDSNA01 is the most common
identifier and stands for ( Global Proxy? ) Mobile Data Services
North America. The '01' is often '5c' but almost always one or the other.

This is a gigantic Server Farm in Canada that is basically just a
regular BlackBerry Enterprise Server which has been opened up
to users who don't have their own BES Server. It acts as a
Proxy for all Internet requests for the default BlackBerry browser.

* ConnectionCID=??

?? Undocumented ?? - It's not in the list above but I have seen it.

Anybody know anything about when/why you want to use a specific CID?

* SpecificUID=S64037865

?? Undocumented ?? - Only appears when a VERIZON device is using BIS?

* ConnectionTimeout=120000

Value is in milliseconds

* EncryptRequired=true

Only valid if talking to a BIS or BES Server. If 'true' then the
request data is encrypted between your device and the BIS/BES Server.

* retrynocontext=true

?? Undocumented ?? - Not really sure what this means at all.

So... can anyone "fill in the blanks" a little more here for the whole
developer community?

Thanks in advance.
kberry

[rnickel]

How about a list of HTTPS ones as well?

[kberry]

So no one has a clue what these parms do?
I'm finding that hard to believe.

[richard.puckett]

Obviously, I can't speak for anyone else, but I have no idea what they do. This is the kind of thing one would think would be documented somewhere, but that seems not to be the case for some reason.

[Scramblejams]

Originally Posted by kberry

Does anyone have a clue what some of these undocumented
parameters are that the RIM BlackBerry browser is using when
it goes to make its calls to 'Connector.open()'??

Hi kberry,

I'm starting to look at this myself after discovering that my newly-written app only wants to chat via Wifi. Can you tell us how you pulled those parameters, so I can see what my 8320 on Tmobile is doing?

In case you haven't seen it yet: Back in '06 RIM published a white paper, "Managing Wireless Data Transport in the BlackBerry solutions v4.0". It's of course getting old, but I was skimming it and found a mention of "deviceside" in it. It's in two parts at the following links:

Managing Wireless Data Transport in the BlackBerry Solutions V4.0 - Part 1: Understanding TCP and HTTP Transport Options for Java Applications for BlackBerry - Whitepapers - ZDNet Australia
Managing Wireless Data Transport in the BlackBerry Solutions V4.0 - Part 2: Understanding Alternative Transport Options for Java Applications for BlackBerry - Whitepapers - ZDNet Australia

(Sorry for the registration-required links, I couldn't find it openly available anywhere.)

Steve

[bdowling]

deviceside and many other connection parameters are described in the standard API docs: RIM Device Java Library: Class Connector

The undocumented ones are interesting. Could it be possible that they are operator specific extensions?

How did you manage to discover these?