Re: [Nxtcommand-developers] Making Icommand ready for different NXTCOMM implementations

[Peter J. <ptg...@ch...>]

Puttng the NXTComm interface in package 'icommand' would even be better.
I need  this interface to support multiple implementations.

Then I do not need an Interface NXTCommand.

This would however mean a "bigger" change in the API.

NXTComm.open() and NXTComm.close() instead of NXTCommand.close()

Peter.

On Thu, 2006-11-09 at 02:23 +0100, Peter Joosten wrote:
> On Thu, 2006-11-09 at 02:21 +0100, Peter Joosten wrote:
> > We should separate API (for end users) from implementation.
> > 
> > At this moment from the icommand.nxtcomm package the NXTCommand class is
> > part of the API (method close()).
> > 
> > package icommand.nxtcomm should NOT be part of the API
> > 
> > Proposal:
> > 
> > Make an interface NXTCommand in the package icommand.platform.nxt
> > with open() and close() methods.
> > 
> 
> Putting the interface in the "icommand" package would be a good
> (/better?) alternative !
> 
> > Change access modifiers in icommand.nxtcomm to package (= no access
> > modifier) as much as possible to prohibit access by end users. 
> > 
> > In the distribution Javadoc of package icommand.nxtcomm will not be
> > included, since it is no longer part of the API.
> > 
> > Peter Joosten.
> > 
> > 
> 
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Nxtcommand-developers mailing list
> Nxt...@li...
> https://lists.sourceforge.net/lists/listinfo/nxtcommand-developers