On 15 Jan 2015 at 10:32, Moshe Rubin wrote:
I would therefore like to briefly summarize what my company's needs are, what problems I've encountered, and a suggested solution for having ASIO support WinRT. [snip] We therefore propose creating a new socket service class for WinRT (we will refer to this new service class as winrt_winsock_socket_service) . This new service will be similar to reactive_socket_service: the stream_socket_service.hpp include file shows the following:
Instead of publically telling everyone what you think Chris hasn't done and what he should do, you might consider approaching him with a view to contracting him at his hourly rate to improve WinRT support in ASIO, or even just asking him how you can best help him to make this happen. Instead of writing to this list, I'd also start with logging an issue at https://github.com/chriskohlhoff/asio/issues, and instead of the commanding and impatient tone you might try indicating you are willing to pay Chris for the improvements according to how Chris thinks they should be implemented. If you're lucky, Chris may create time for your improvements sooner rather than later. He may even do it for free. You can of course also do the work yourself and send him a pull request on github, but I've noticed he usually won't merge any large new pull requests he hasn't solicited. I assume they conflict with his other feature work branches, or don't have the quality Chris is looking for. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/