[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
question about Common C++ 2 serial class
From: |
Tim Esselens |
Subject: |
question about Common C++ 2 serial class |
Date: |
Wed, 16 Oct 2002 17:02:43 +0200 |
User-agent: |
KMail/1.4.7 |
Hi,
I've been using your serial class for a HA (high availability) project. I've
managed to get 2 machines to ping eachother over serial line. But there is a
rather big problem coming up. If I flush (this->flush()) my object
(SerialBeat: public TTYSession) the thread blocks, flushOutput() doesn't seem
to be flushing at all.
So, the problem I'm having is quite simple, how to flush in a nonblocking kind
of mode, so after n msecs of 'unflushability' it could start throwing errors.
I only hope the answer is as easy as the question.
If this is not possible for some reason, is there a way around this (still
using your serial class ofcourse)? I need to detect the other side is down,
that's really it (maybe something the serial protocol allready includes, but
I'm new to serial lines, so I wouldn't know).
kind regards,
Tim Esselens
ps: NEWS stated sending questions to dyfet, README to bug-commoncpp, I did
both <g>
- question about Common C++ 2 serial class,
Tim Esselens <=