Re: PPP object questions

[snip]

> If your link is using XON/XOFF flow control use setLocalACCM and
> setRemoteACCM to set an ACCM of 0x000a0000. The setting of an ACCM 
> value
> is not dependent on server/client operation.

I understand how ACCM works, but I was confused when one should use a 
setRemoteXXX() vs. a setLocalXXX() call, including for the ACCM 
methods.

My take on any of these is that if you are a server, you need to be 
setting the "remote" methods to tell the remote peer what to do.  Is 
this true in general for these?

> freePort() forces the PPP native library to release the serial port
> object. This allows the serial port object to be used by the 
> application
> again. The application should not read or write to the serial port
> between the up() and and freePort() methods.

Two things confuse me: the documentation doesn't mention that this 
needs to be called, and also the PPP.java source code calls this method 
in the LCP "layer down" and LCP "layer finished" events.  Will these 
events always happen, and if not, is a call to freePort() then 
required?  Do you recommend its use for cleaning up?

> finish() terminates a sleeping read thread within the PPP native 
> object,
> kills an internal timer thread and kills an internal queue thread.

Again, is this required?  The docs don't say so.  Do you recommend its 
use for cleaning up?

> freeNativeInterface() releases native resources used by the PPP object.
> This should be the last of the methods called.

I note that the PPPClient example doesn't call this.  Is this 
recommended for cleanup?  Again, the docs say nothing.

I would like to request that the documentation for PPP is updated to 
included the recommended cleanup procedure for the various use cases.

Much thanks,

	-Shawn

_______________________________________________
TINI mailing list
TINI-6tN4nzCoH/[email protected]
To UNSUBSCRIBE, edit your profile, or see list archives:
http://lists.dalsemi.com/mailman/listinfo/tini