RE: [A5:RT] Minimum J2ME Specs and Strategy
"Andrzej Jan Taramina" <[email protected]> Mon, 06 Jan 2003 13:08:15 -0500
| Newsgroups | gmane.comp.jakarta.avalon.apps.devel,gmane.comp.jakarta.avalon.devel |
|---|---|
| Organization | Chaeron Consulting Corporation |
| Message-ID | <3E197FBF.30042.61A0A848@localhost> |
Marc and others have assumed: > However, most development is currently going on on CLDC + > MIDP capable cell phones and PDA devices and a framework for componentized > services could be a great product on these platforms. Be careful of making the cell phone/PDA assumption. I believe there is a more pressing and larger market opportunity in the embedded systems arena (eg. manufacturing process control, and the like). The consumer device market is probably not as attractive a platform for Avalon 5 in this respect. A slimmed down Avalon container/framework would be ideal for this market segment since lifecycle support, modularity and container support will be key to support such embedded controllers. MIDP/CLDC (and CDC shortly) are supported by some embedded processors already. But regardless of that, MIDP/CLDC provides a good example of the constraints that any embedded procesor will be faced with in implementing Avalon 5. Many parts of the MIDP spec are targeted at Cell/PDA devices....for example, the LCDUI rendering classes, which will NOT be required for an embedded container implementation. I would not target Avalon 5 at MIDP/CLDC specifically....but just use those specs as a good "constraints baseline" for limited capability embedded environments. Andrzej Jan Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com