This week's giveaway is in the Java/Jakarta EE forum.
We're giving away four copies of Java EE 8 High Performance and have Romain Manni-Bucau on-line!
See As an example of this, the MIDP Specification does not mandate TCP nor UDP but many applications (e.g. Chat client, Real Time Games etc.) rely on these protocols. Several Carriers/Handset Manufacturers see the need for these protocols and have implemented them. The MIDP Connection Framework is generic there are no additional classes required by the API (i.e. No need to use specific OEM classes).
This particular area is a minefield when you go onto the device however. Streaming applications have demonstrated a variety of implementation bugs with handset manufacturers (the Sprint devices and the Motorola devices in particular). Each have their own workarounds etc.
This leads me onto my question regarding the book. I am wondering how much "hands-on" information there is relating to particular devices. For example, the Nokia devices have some interesting behaviour relating to HTTP. Some devices are notoriously slow to decode PNG images. The Sanyo leaks CPU cycles like a sieve when you're using the connection framework. This sort of information would be incredibly useful and it would save developers hours of newsgroup searching.
Paul Kelcey
Ranch Hand
Posts: 55
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The book covers the APIs thoroughly but doesn't get into device issues. I believe that there is a lot of this type of information scattered around the Internet, and I agree that it would be very helpful to have a central repository. I've been giving it some thought but haven't come up with a plan yet.
Consider Paul's rocket mass heater.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!