Montag, 2. November 2009

MIDP3.0

MIDP 3.0 is still a draft an in discussion.... still...

If you start looking at it, as a BlackBerry developer it's sounds disappointing. We know about libraries and auto-run applications, that's our daily work. But I think having this standardized is always a good news.

But there is more: Sun just published a new article about a Midp 3.0 feature: inter process communication
http://java.sun.com/developer/technicalArticles/javame/midp3_enhance/
You can use Connector.open to another midlet and you can wait for incoming events as a listener.

But another time:
as a BlackBerry developer there is nothing new. We have a lot of possiblities for IPC: the RuntimeStore , global messages (I have to admit I heard about them just weeks ago, never used it).
But even without RIM APIs there is JSR 211: CHAPI (see the blog entry yesterday, seems this is the CHAPI month ;)).
Do we really need MIDP 3.0 IPC and events?
I can send custom data to another app via CHAPI. This could be based on custom mimetypes or directly via using the handler ID.

For me: another time I do not see the any need for MIDP 3.0
RIM probably will introduce MIDP 3.0 at some point. A good thing or a waste of development time?

Keine Kommentare:

Kommentar veröffentlichen