I didn't notice any mention of a currentOwner field. When that issue
cycles to the top of the priority pile I'll do some more tests and make
sure.
boB
Emmanuel Lecharny wrote:
boB Gage wrote:
Opps!! Forgive the previous, hit send before I even started
typing.... :-(
Like I said, it's not really my call. Any development I do wrt this
project is owned by my boss, not me -- I've got no problems
contributing to the project, but I don't own what I write.
Yea, personally, had I been the one making the decisions, I would've
gone with Mina 1.x (whatever the last stable release was) and planned
on upgrading to 2.0 after it was finalized. But it's way too late
to go back now. :-)
If ya really do want the whole picture.... :-)
I'm also seeing a flow control problem. Once attempting a protocol
requiring hardware flow control (CTS/RTS) on a port, that port cannot
be used again. Once the RTS/CTS-desiring protocol uses the port
(and fails to get the response it wants) all further connections
generate PortInUseException's on open attempt until the program is
stopped and restarted. This particular issue has only been seen on
Windows systems -- the same code running on a Linux machine works
just fine.
I guess that Windows 'freeze' the port for a while... Anything about
the currentOwner field ?
PS: I'm not a serial kill^H^H^H^H specialist at all. Julien is.
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
