Using HTTP vs UDP vs Socket in J2ME
By: David Hemphill
In the case of MIDP, the specification only requires support for HTTP, although many devices support datagrams and sockets as well, because these protocols are needed to implement HTTP. However, before making commitments to datagrams or sockets it is a good idea to make sure they are supported on the platforms you are targeting.
Because HTTP is guaranteed to be supported by MIDP this is usually the best protocol choice due to portability. HTTP moves through firewalls easily since it generally operates over port 80. However, of the three protocols discussed, HTTP incurs the most overhead, which may drive up the user's cost of using the application on the network.
Datagrams, on the other hand, tend to have far less overhead and can be easier on the end-user's budget. The caveat, as discussed previously, is that the application must take on the task of ensuring that all data arrived at the other end and that the order of that data received is correct.
Finally, sockets fall somewhere in the middle of HTTP and datagrams in that data sent over a socket is managed by the protocol, but requires fewer network resources than HTTP. This means that the application does not have to concern itself with making sure data is received on the other end. Sockets are generally a lighter-weight option over HTTP since the application controls when the end points communicate. HTTP, on the other hand, must make several trips between the end points to exchange header information as well as the data.
The GCF provides a lot of functionality and standardizes how connections
are established throughout the J2ME architecture. The GCF is extensible as
well, allowing manufacturers to support their own interfaces and connection
types. In some cases a manufacturer may use the GCF to support streaming
multimedia content with a special connection or for establishing connections
to a GPS receiver. Having this kind of flexibility prevents J2ME from being
constrained to a common set of protocols while maintaining consistency
throughout the architecture.
Archived Comments
1. it's good and very best
View Tutorial By: rushikesh at 2014-02-04 11:28:42
2. is good bot not full
View Tutorial By: amin parishani iran at 2010-07-07 10:51:33
3. sir how can i access url in one click
View Tutorial By: mohit at 2010-05-28 23:10:23
4. sir very well subject is to continuted the java source code
View Tutorial By: G.venkata siva naga kumar at 2009-11-06 01:13:02
5. best site ever.
View Tutorial By: rehan ahmed at 2008-12-10 02:21:32
Comment on this tutorial
- Data Science
- Android
- AJAX
- ASP.net
- C
- C++
- C#
- Cocoa
- Cloud Computing
- HTML5
- Java
- Javascript
- JSF
- JSP
- J2ME
- Java Beans
- EJB
- JDBC
- Linux
- Mac OS X
- iPhone
- MySQL
- Office 365
- Perl
- PHP
- Python
- Ruby
- VB.net
- Hibernate
- Struts
- SAP
- Trends
- Tech Reviews
- WebServices
- XML
- Certification
- Interview
categories
Related Tutorials
Code sample to Send SMS from a J2ME application.
Adding your own Application icon for your J2ME application (jar file)
Play a multimedia file in J2ME Program (Audio/Video) using MMAPI
Using HttpConnection in J2ME (Retrieve web content from a website to a phone)
Using HTTP vs UDP vs Socket in J2ME
RMSCookieConnector - Using Cookies in J2ME
Client Server in J2ME (Socket Programming sample)
Datagrams in J2ME (UDP Programming sample)
POST UTF-8 encoded data to the server in J2ME
Using alerts and tickers in J2ME
Using List to create a Menu and Menu items in J2ME
lists, forms, choices, gauges, text fields, text boxes in J2ME
Timer and TimerTask example in J2ME