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

BTW. I could provide an implementation if desired...

> -----Original Message-----
> From: Marc Schier 
> Sent: Friday, January 03, 2003 2:07 PM
> 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]>
> > 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:[email protected]>
> For additional commands, e-mail: 
> <mailto:[email protected]>
>