[wx-discuss] wxSocket rewrite using Boost.Asio
Vadim Zeitlin
vadim at wxwidgets.org
Tue May 27 16:14:44 PDT 2008
On Tue, 27 May 2008 16:06:10 -0700 "William H. Schultz" <whschultz at cedrus.com> wrote:
WHS> I just mean that there's documented functionality that is close enough
WHS> to useless that it could be argued that it's not available.
Maybe but we'd have to look at each case in details. To me personally more
than half of wxSocket code seems broken but if we throw everything I don't
like away there won't be much left. Again, I'm not arguing for keeping
compatibility just because I like to annoy people but because it doesn't
make sense to write a wrapper around ASIO if it's not compatible -- if the
compatibility isn't important, people should just use ASIO directly.
WHS> According to sckaddr.h, IPv6 isn't implemented.
Are you looking at the trunk? Anyhow, this wasn't about compatibility but
just a "FYI" remark.
WHS> I've started today on figuring out how to organize the Asio classes
WHS> within the existing wxSocket classes. Asio is designed so that the
WHS> difference between IPv4 and IPv6 is incredibly transparent... so much
WHS> so that wxIPaddress will probably no longer be an abstract class.
WHS> IPv6 functionality needs to be seamless or the code will be dead
WHS> within a couple of years.
Yes, I think it makes more sense to have a single wxIPaddress class.
Good luck,
VZ
More information about the wx-discuss
mailing list