Closed GoogleCodeExporter closed 9 years ago
Hm .. I don't really get your point. I don't have practical experience with
Blackberry devices, could you try to describe the desired feature in other
words?
Original comment by obensonne@googlemail.com
on 25 Nov 2009 at 10:27
It's more of a firewall issue than a Blackberry issue, per se.
All internet connections from my Blackberry originate from an IP inside the
corporate
network. The corporate network has a firewall, and the only way to make
connections
outside it is via the HTTP proxy.
http://www.xk72.com/midpssh/ for the BlackBerry has an HTTP proxy option in the
network settings, perhaps you could look at how they implement it.
Original comment by LaBlua
on 25 Nov 2009 at 10:48
I'll have a look into it.
Besides that, I remember a user (using a Blackberry with WiFi support) reported
that
the option 'interface=wifi' had to be set when setting up a WiFi connection in
the
Remuco client. This told the device to not use the phone network (or BIS) for
connections but the WLAN interface. Is this a solution for you?
Original comment by obensonne@googlemail.com
on 25 Nov 2009 at 11:22
Unfortunately not, as my Blackberry (Curve 8330) does not have WiFi. My linux
box
doesn't have Bluetooth. So WLAN via HTTP proxy is my only option.
Original comment by LaBlua
on 25 Nov 2009 at 11:52
I'll work on this ASAP. Stay tuned for testing.
Original comment by obensonne@googlemail.com
on 2 Dec 2009 at 10:01
Just stumbled upon this:
http://www.blackberry.com/developers/docs/5.0.0api/javax/microedition/io/Connect
or.html#socket
They mention an option 'deviceside' to control if using direct TCP connections
or
proxy TCP connections. What happens if you set the option deviceside=true in the
client's WiFi configuration screen?
Original comment by obensonne@googlemail.com
on 4 Dec 2009 at 11:13
Yes! Setting "deviceside=true" in the config screen allows remuco to work.
It seems a tad prone to losing connection and not realizing it, but other than
that
it is working for me now, thanks!
Original comment by LaBlua
on 16 Dec 2009 at 1:53
Good news. I don't think the connection loss is a Remuco issue. The only thing
you
could try is to change the interval at which the client pings the server. By
default
this is set to 15 (or 25) seconds. If you reduce this value, broken connections
get
recognized faster. In the 0.9.2 client the ping interval can be set in the
options
screen.
I'll add the "deviceside" option info to the wiki.
Cheers,
Oben
Original comment by obensonne@googlemail.com
on 16 Dec 2009 at 8:22
Original comment by obensonne@googlemail.com
on 8 Mar 2011 at 6:38
Original issue reported on code.google.com by
LaBlua
on 25 Nov 2009 at 4:18