" type="cite">" type="cite">
For the question about the relationship between CLDC AccessPoint and
The AccessPoint abstration is focused onTCP/IP network interfaces.
Its origin was based on the operating system or device managing
the underlying networking stack. The application can pick an interface
and may want/need to be aware of its characteristics but cannot control it.
Recent suggestions/improvements have expanded that somewhat but it
is still primarily an abstraction for a networking stack.
The MEEP CellularNetwork and Subscriber encapsulate information about
wide area networking and the operator managed subscriber information
found on SIM cards. These abstractions provide access to cellular networking
properties and controls. As above, the application needs only an abstraction
for the network and (mostly) leaves the management of the cellular network to
Most applications can operate effectively with only the AccessPoint information
and do not need control over cellular functions in most cases and the
separation makes the API easier to understand and use.
8.) javax.microedition.event: A general question about this package: why such a generic event package ? In the past several classes had some listener functionality and they received "their" events through this listener. To me it seems a bit confusing to have such a generic event mechanism which then again contains events of all sorts.
Actually the more generic solution was inteded
to ease the confusion. :-)
Roger> The event package enables two kinds
of event that are not
For specific APIs, each API design should
include listeners with event
[jsr361-observers] [jsr361-experts] Re: some remarks