AW: [A5:RT] Minimum J2ME Specs and Strategy

just a few notes ...

 1) basicly you wouldn't work with the CDC API,
    instead if you choose CDC you would work with
    a Java VM that implements the Personal Profile.

    Personal Profile is the successor of PersonalJava
    but all Win CE/Pocket PC 2002 handhelds are still
    shipping with a PersonalJava VM. if you want to
    evaluate a Win CE VM i would suggest CREME.

    -> http://www.nsicom.com/

 2) the Sony Ericsson P800 cell phone runs both the MIDP
    and PersonalJava Profile. that phones ships with a
    rich set of Java APIs (like location based services
    etc.).

 3) i don't understand why someone would be interested
    in implementing a A5 container on MIDP. you should know
    that the memory limit is mostly around 100KByte on those
    devices and if you start using a XML parser i will reach
    that limit very soon.

    even if you'll manage to stay within that range doesen't
    mean that there is enough space left to run an app in that
    container.

    i am now developing about three years with J2ME and it was
    allways a challenge to bring both, business logic and the
    app server, on a MIDP device. for example, if you manage to
    run both the container and the app on a Palm Pilot (which
    supports MIDP), there would still be the raimaining problem
    that it takes about 5 - 10 minutes to start the whole thing.

    so the ultimate choice would be CDC/Personal Profile/PersonalJava.

 4) speaking about XML parsers - if you decide to stick with
    MIDP i would suggest the following XML parsers.

     - kXML 2 -> http://kxml.org/

     - XPP -> http://www.extreme.indiana.edu/xgws/xsoap/xpp/index.html

    IBM's developerWorks did some performance tests and
    as i remember kXML 2/XPP are outperforming kXML 1.

 5) there is already a J2ME JINI environment. allthough i wouldn't
    use JINI as an argument for CDC, cause in most cases you might
    consider to use the J2ME JXTA client. and last but not least
    there are already some Linda Tuplespace implementations for
    J2ME which are providing many JINI like features.

regards

daniel s. haischt
--

> -----Ursprüngliche Nachricht-----
> Von: Noel J. Bergman [mailto:[email protected]]
> Gesendet: Samstag, 4. Januar 2003 05:47
> An: Avalon Developers List
> Betreff: RE: [A5:RT] Minimum J2ME Specs and Strategy
>
>
> Marc,
>
> I expect that within a very few years the current target platforms for the
> CLDC will be running the CDC instead.  Stinger-class cell phones,
> linux and
> WinCE PDAs, etc., are already fully capable of supporting the CDC.  And it
> is far easier for Sun to promote JINI on CDC devices.
>
> In any event, it is still a decision to make, and the CDC is far more of a
> viable platform for hosting an Avalon container as such are currently
> understood.
>
> 	--- Noel
>
> -----Original Message-----
> From: Marc Schier [mailto:[email protected]]
> Sent: Friday, January 03, 2003 17:07
> To: 'Avalon Developers List'
> Subject: RE: [A5:RT] Minimum J2ME Specs and Strategy
>
> CLDC is here to stay, especially on smart-devices and cell
> phones.  CLDC 2.0
> will include floating point arithmetic and is scheduled to be
> released soon.
> From my experience I agree that the http://java.sun.com/products/cdc/ (+
> Personal Profile) is much better suited for a framework like
> Avalon. In such
> an environment you can implement containers that are much more
> sophisticated. 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.  Please
> take a look at
> http://kxml.enhydra.org/ or MinML.  They could be useful parsers for the
> configuration objects.  We could use Tweety as the J2ME container and add
> kXML configuration and mandate that all J2ME compliant components must be
> thread-safe and we will have our j2me compliant container today.  I think
> thread-safety is tolerable in such a constraint environment. (just my 2c)
>
> > -----Original Message-----
> > From: Berin Loritsch [mailto:[email protected]]
> > Sent: Friday, January 03, 2003 1:54 PM
> > To: 'Avalon Developers List'
> > Subject: RE: [A5:RT] Minimum J2ME Specs and Strategy
> >
> > > From: Noel J. Bergman [mailto:[email protected]]
> > >
> > > Berin,
> > >
> > > Alternatively, the Avalon Community could take the view that
> > > CLDC devices are going to go the way of the Dodo, and focus
> > > on the CDC as the low-end configuration.  That would provide
> > > a far more compatible environment, dealing primarily with
> > > scale instead of incompatibilities.
> >
> > Where is the link for CDC?  I saw MIDP and CLDC.
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[email protected]>
> For additional commands, e-mail:
> <mailto:[email protected]>
>
>
>