> What's worse is that some of the carriers don't publish the correct
> information about this. We had a potential business deal with a
> Canadian company, and we could never get a direct connect gateway to
> work.
Some carriers support only WAP, not full internet connection.
WAP is implemented on top of TCP/UDP. The device has an IP address and can
open direct TCP connections. Only the phone's WAP browser needs the WAP
gateway to translate WML into binary stream and essentially deal with the
WAP protocol specifics, on top of the regular TCP/UDP connectivity. Java
midlets do not use the WAP gateway but connect directly.
Some carriers intentionally restrict traffic, for security reasons or
because they choose to offer different charges for WAP (phone browser, small
data volume) and internet connections (used for Java apps and internet
access for laptops / PDA as well, in much larger volume). Some carriers
offer only WAP, restricting all connections but the ones to the WAP gateway.
> HTTP access in Java will fail after 12 or so packets IF you don't have a
> direct connect (0.0.0.0) gateway setup. The fact that this works for
> the first 10 or so I/O attempts via. the default WAP gateway and then
> fails is a major bug IMHO.
I haven't verified this, but Series 60 devices seem to route all HTTP
connections via the WAP gateway if it is specified, regardless of weather
the connection originates from the WAP browser or not. The WAP gateway often
has a size limitation for the downloaded data, or there may be other
conflict with the operator configuration. Seems like a carrier-related
problem. There are many Series 60 Java applications using HTTP connectivity
without problems.
Nik
Received on Thu Nov 13 22:44:39 2003