From: ïÌÅÇ áÂÒÏÓÉÍÏ× (olegabr_at_[hidden])
Date: 2006-12-20 11:21:12
Christopher Kohlhoff wrote:
> Yes, it is already on my todo list to do something about this for asio
> (probably adopting the approach used by the interprocess library rather
> than the bridge pattern). However there are plenty of other things that
> have a higher priority, so it won't happen for quite a while.
Thank you. I'm completely satisfied by this answer with one amendment: This issue should be covered by asio documentation. for example in FAQ.
> Yep. Another potential disadvantage of a separated model is gratuitous
> copying or memory allocations resulting from mapping external to
> implementation types. For example, scatter-gather operations use WSABUF
> on windows -- if that type is to be completely hidden, then I need to
> copy the buffer pointers to a separate array first.
> While I'm hopeful these problems can be solved, they are why I'm leaning
> towards the approach used by interprocess as a simpler solution. That
> is, to declare/define the required types and functions myself instead of
> including windows header files.
sounds very promising!
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk