One more thing to consider: network latency.
Requesting data over HTTP requires one round-trip for data, in addition
to TCP session setup. The latter can be all but eliminated by using HTTP
connection keep-alive.
DB protocols can be more chatty, requiring more network round-trips to
get the same data. This can result in lowered performance.
-- Kostya
22.08.2010 13:49, Mark Murphy пишет:
On Sun, Aug 22, 2010 at 5:32 AM, Tim<[email protected]> wrote:
A direct connection to a remote database is perfectly secure, usable
and technically possible particularly if the Android device is
connecting via a secure wi-fi network or a GPRS/3G network where the
SIM is part of a private APN. Unlike J2ME for example, the Android
framework supports full database JDBC connectivity.
However, the database connection protocols are designed with reliable
LANs in mind. Neither WiFi nor 3G are reliable, simply because device
owners have the audacity to move around, sometimes while doing the
unthinkable and actually using their devices. :-)
--
Kostya Vasilev -- WiFi Manager + pretty widget -- http://kmansoft.wordpress.com
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
