• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

J2ME advantage over WAP

 
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all.

This is simple a question, but I'd like to hear the answers from folks here at JavaRanch:

What are the main advantages of programming an application like Sun's Smart Ticket (or other enterprise app) in J2ME rather than making it using WAP/WML pages?

Thanks in advance.
 
Ranch Hand
Posts: 524
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
Well the main advantage I see the that the J2ME applications can provide dynamic content where as WAP is providing static content. So it is possible to have a rich client application in J2ME.
Hope this helps.
 
Ranch Hand
Posts: 101
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
But dynamic content can be delivered in WML format by using servlets and JSP server-side. I think the main reasons you would want to use a thick-client on a mobile platform would be similar to the reasons you would on a full desktop. It really depends on whether a thick client or thin client fits your needs best.
 
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi-

The main advantage with J2ME app that I see is the ability to access the peripherals on the device(like barcode scanner, printer) which I believe we cannot do using the WAP.

Hope this helps
Satyam.
 
Ranch Hand
Posts: 102
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Satyam Kothapally:
The main advantage with J2ME app that I see is the ability to access the peripherals on the device(like barcode scanner, printer)



Actually, you usually can't do that from J2ME either. That would require some custom extensions to MIDP 1.0.

For client/server architectures, there are some simple advantages to using a MIDlet like speed and fancy UI's. You may also improve performance using custom protocols, caching, and pre-fetching. You can't do that over WAP. A MIDlet also gives you local storage for user settings that is more reliable and more controlled than browser cookies. The biggest advantage is probably reducing the number of round-trips and/or background downloading. All these things make the system more pleasant to use.

Why use MS Outlook instead of Hotmail?

William Frantz
http://sprintdevelopers.com
 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
There is yet another advantage by using j2me over WAP. In WAP u need to be in always connected mode, but in j2me one could connect whenever required. Hence applications could still work when user is out of coverage area.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic