asio review results - asio accepted

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

asio review results - asio accepted

Jeff Garland
Cross-post from development list

----
All -

I'm pleased to announce that asio has been accepted into Boost.  As
usual with a Boost review, the asio review generated plenty of
discussion, issues, and controversy.  Comments ranged from high praise,
including success stories of projects in production, to serious design
concerns and issues.  On balance, in my judgment, asio provides a
generally solid library that is ready for inclusion into the Boost
library -- providing key functionality in an area that developers have a
strong need.

Of course, like anything else, asio is not perfect -- a number of key
issues were uncovered during the review.  In terms of required changes
I'm only going to cite a few:

- Fixes to dynamic memory allocation issues
- Interface changes to support ipv4 and ipv6 seamlessly at runtime
- Improvements to support strongly typed socket interfaces

Chris has communicated a couple possible solutions to the memory
allocation issue and I'll ask that the interface and other changes for
this issue continue to be discussed on the Boost list so consensus can
be achieved on the best resolution.

Other key improvements that should be explored as future enhancements
include:

- Possible removal of some of the c-style interfaces
- Exploration of higher level iostream integrations
- Performance improvements
- Improved documentation (wouldn't be Boost w/o this one)

Chris has a much longer list of changes garnered from the review and is
well on his way to addressing many of them.

Note that there were several threads and discussions about performance,
which is particularly critical for the domain covered by asio. One of
the performance issues is the dynamic memory allocation issue cited
above.  In general, the reviewers have extremely high expectations here.
However, after reviewing the discussion and library it's my belief that
many developers will find asio performance sufficient to build
significant projects with only the memory allocation changes. I expect
Chris will be able to address some of the other performance issues cited
by reviewers in asio over time.

Once again I'll apologize to the Boost community for the delay in the
review results.  The delay was entirely due to my own personal
scheduling issues and should not reflect on asio in any way. Thanks
again to all the reviewers for their effort and especially to Chris for
his tremendous effort in bringing asio to Boost!

Jeff





_______________________________________________
Boost-users mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-users
Reply | Threaded
Open this post in threaded view
|

Re: asio review results - asio accepted

RIVASSEAU Jean Noel
Could you just explain very shortly what Asio is about ?

Jean-Noël

-----Message d'origine-----
De : [hidden email] [mailto:[hidden email]] De la part de Jeff Garland
Envoyé : jeudi 23 mars 2006 15:18
À : [hidden email]
Objet : [Boost-users] asio review results - asio accepted

Cross-post from development list

----
All -

I'm pleased to announce that asio has been accepted into Boost.  As
usual with a Boost review, the asio review generated plenty of
discussion, issues, and controversy.  Comments ranged from high praise,
including success stories of projects in production, to serious design
concerns and issues.  On balance, in my judgment, asio provides a
generally solid library that is ready for inclusion into the Boost
library -- providing key functionality in an area that developers have a
strong need.

Of course, like anything else, asio is not perfect -- a number of key
issues were uncovered during the review.  In terms of required changes
I'm only going to cite a few:

- Fixes to dynamic memory allocation issues
- Interface changes to support ipv4 and ipv6 seamlessly at runtime
- Improvements to support strongly typed socket interfaces

Chris has communicated a couple possible solutions to the memory
allocation issue and I'll ask that the interface and other changes for
this issue continue to be discussed on the Boost list so consensus can
be achieved on the best resolution.

Other key improvements that should be explored as future enhancements
include:

- Possible removal of some of the c-style interfaces
- Exploration of higher level iostream integrations
- Performance improvements
- Improved documentation (wouldn't be Boost w/o this one)

Chris has a much longer list of changes garnered from the review and is
well on his way to addressing many of them.

Note that there were several threads and discussions about performance,
which is particularly critical for the domain covered by asio. One of
the performance issues is the dynamic memory allocation issue cited
above.  In general, the reviewers have extremely high expectations here.
However, after reviewing the discussion and library it's my belief that
many developers will find asio performance sufficient to build
significant projects with only the memory allocation changes. I expect
Chris will be able to address some of the other performance issues cited
by reviewers in asio over time.

Once again I'll apologize to the Boost community for the delay in the
review results.  The delay was entirely due to my own personal
scheduling issues and should not reflect on asio in any way. Thanks
again to all the reviewers for their effort and especially to Chris for
his tremendous effort in bringing asio to Boost!

Jeff





_______________________________________________
Boost-users mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-users


_______________________________________________
Boost-users mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-users
Reply | Threaded
Open this post in threaded view
|

Re: asio review results - asio accepted

Bugzilla from markus.schoepflin@comsoft.de
RIVASSEAU Jean Noel wrote:

> Could you just explain very shortly what Asio is about ?

See http://asio.sourceforge.net/

Markus

_______________________________________________
Boost-users mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-users
Reply | Threaded
Open this post in threaded view
|

Re: asio review results - asio accepted

RIVASSEAU Jean Noel
In reply to this post by Jeff Garland
Thanks, actually I wrote the first message because I do not have access to the web right now, and would have liked a short explanation on the ML, but I should have explained that...

I'll have a look at it this evening.

Jean-Noël

-----Message d'origine-----
De : [hidden email] [mailto:[hidden email]] De la part de Markus Schöpflin
Envoyé : jeudi 23 mars 2006 15:39
À : [hidden email]
Objet : Re: [Boost-users] asio review results - asio accepted

RIVASSEAU Jean Noel wrote:

> Could you just explain very shortly what Asio is about ?

See http://asio.sourceforge.net/

Markus

_______________________________________________
Boost-users mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-users


_______________________________________________
Boost-users mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-users
Reply | Threaded
Open this post in threaded view
|

Re: asio review results - asio accepted

Jeff Garland
RIVASSEAU Jean Noel wrote:
> Thanks, actually I wrote the first message because I do not have access to the web right now, and would have liked a short explanation on the ML, but I should have explained that...
>
> I'll have a look at it this evening.

The blurb:

asio is a cross-platform C++ library for network programming that
provides developers with a consistent asynchronous I/O model using a
modern C++ approach.

Jeff
_______________________________________________
Boost-users mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-users