Originally posted by Paul Kelcey:
- Does it cover any of the issues with working with real devices (e.g. which devices work well in particular areas but not so well in others)? Some devices support image transparency and some do not for example.
- There was mention of communication protocols. Is this restricted to HTTP (which for MIDP 1 is the only mandated protocol) or does it cover TCP and UDP?
- Is the book mainly dealing with J2EE technologies on the server and working with a MIDP client via HTTP. e.g. Writing an application using the high level user-interface widgets and connecting say to a JSP pointing to EJBs?
- Does it cover MIDP 2.0 at all?
Originally posted by Paul Houser:
I would think developing games in Java on mobile devices would just be pointless. From experience I know Java programs already run slow with the limited specifications of a Pocket PC (mine runs on a 206 mHz ARM and only has 32MB of ram), and I would think games would be out of the question, especially for devices like the Palm and mobile phones that are even more limited than my iPaq.
But the problem with TCP is not really the device support. Wireless networks often do not support TCP natively -- they sometimes add TCP as a compatibility layer ON TOP OF HTTP.
Originally posted by Lion Z. Li:
I'd been wondering how come in MIDP-1.0 HTTP is supported while TCP an option. It's quite a stange way of thinking in traditional network protocol stack because HTTP is built on top of TCP. Is above anwsers my question too? And in wireless networks, Does it mean that using TCP can be less efficient than using HTTP(for network transmision)? Which do i choose in practice if both are available? Can you please gvie more knowledge or references to where i can find information about this.
Originally posted by Peter Cheng:
1. If we want to support j2me, what should we do to enhance JFoxMQ.
2. What technologies should we take into consider in building wireless message?
Originally posted by Ashik uzzaman:
I asked a friend to look for Yuan's Enterprise J2ME book in Calcutta, India as it is yet not available in our country. But coul not manage it yet. I think several chapters of this book wil be helpful during our preparation for SCMAD beta exam.
Originally posted by Michael Yuan:
Yes, for networks that provide emulated TCP/IP layer on top of HTTP, TCP is indeed slower than HTTP. But it depends on the network. The bottom line is: both are slow, high latency networks before 3G arrives.
Originally posted by Ko Ko Naing:
I'm not sure in J2ME context... But what I am understanding is that TCP(Transport Layer) in the OSI model should be faster than HTTP(application layer)... Could u please correct me, if my understanding on it is wrong...