This post originated from an RSS feed registered with Java Buzz
by Fred Grott.
Original Post: WIPI or confusion over Middleware platforms
Feed Title: ShareMe Technologies LLC-The Mobile Future
Feed URL: http://www.jroller.com/shareme/feed/entries/rss
Feed Description: A Weblog about Java programming and digital convergence on mobile devices in such areas as P2P and collaborative technology.
Why do poeple constnatly i an error prone way confuse a closed API not accessible to application coders such as WIPI? One job post recently was attempting to claim that you write mobile applications using C++ to the WIPI middleware mobile platform.
Of course, you can not as the application framework APIs in WIP are in fact Java ME. Part of the confusion may be the lack of a clear definition of what a software platfrom, middleware platform, and etc are in the mobile space.
Some, for example SymbianOS, cover both the MobileOS and Middleware platforms and include Java ME. Than we have hardware solutions that embedd Java ME on chips as both the MobileOS and Middleware platform.
Both Qualcomm Brew and SymbainOS also include their own closed application frameworks in addition to JavaMe. Are we confused yet?