From: Hurd, Matthew (hurdm_at_[hidden])
Date: 2004-01-28 23:04:57
> On Behalf Of Sean Kelly
> What remains an issue in my mind is how far to take this. Socket and
> file classes for each platform at least... what else?
Waitable timers would be the other "main" one I'd guess.
Some process abstractions might be straight forward for "kill" signals
and the windows equivalent.
I would still like to see mutexes, timers, socket i/o and file i/o all
with similar acquisition concepts so there is a hope of marrying them
down the track if it is not done up front.
The other thing I'd like to see is a substitutable framework, like the
synch stuff I posted a while ago, where you can develop to a particular
policy concept, for example a shareable mutex, then substitute a single
threaded or null mutex or anything else in. ACE has had something
similar for many years and it is straight forward. The current
interface does not support such use AFAICT, hence the synch wrapper I
use. I'd be happy to document and clean this up if there is interest.
IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk