[Rxtx] RTS control in RXTX

[Pete Flugstad]

Trent Jarvi wrote:
> My concern is mainly platform neutrality.  We can do some of this but 
> other parts are very MSFT Windows specific.  I suspect that commapi had a 
> Windows developer involved early on based upon some of the functionality 
> already in the API.
> 
> How much of this is just trying to fit as much of the Windows API in as 
> possible vs known usage cases?  If there are usage cases and Unix just 
> can't do it, thats one thing vs advertising features which are just really 
> obscure corner cases at best alongside what everyone uses.

I don't especially care about what Windows is doing - we would like to 
be cross platfor as much as possible.  But it does appear to me that the 
Windows API encompasses all various behaviors (the two RTS behaviors, 
CTS behavior, DTR/DSR behavior) that are currently being used with 
standard RS232 hardware.

And I think it would be best for the javacomm API if it exposed this 
functionality, even if not all platforms implemented them.  As other 
posters in my original thread have noted, both RTS behaviors are fairly 
common.  Right now, on the Windows platform, you literally cannot get 
the old style RTS/CTS (i.e. flow control only in PC->Modem) behavior 
without modifying RXTX - other platforms are probably going to have the 
same problem (unfortunately).

In any case, I'm basically just rattling the cage here - I'm really just 
interested in doing enough to get RXTX working for our projects - I 
could conceivably do something totally custom to us (recognizing the 
RXTX license of course) but then if we ever wanted to move onto newer 
RXTX or another javacomm impl, we'd be in trouble, which I'd like to 
avoid.  So, consider the cage rattled (Bob Jacobsen, Guillermo Rodriguez 
Garcia, et al) :-).

> It is possible to work through much of this.  There are folks looking at 
> an API update [under NDA now?].

Do you mean that there are people doing this (and they're under NDA), or 
are you asking the question?  If you're asking the question; I have no idea.

Pete