Unless you have a problem with the driver in
I was just about to dust that off (update it and/or pull in your
github work) and work it in parallel with proton-159. In theory the 2
together should result in proton working with C++ and Windows
libraries. The additional steps to get a Visual Studio implementation
should be very straight forward after that.
As before, the intent is to get a functional driver (without ssl for
now) that can get people going on Windows. A high performance driver
(with overlapped io presumably) and with ssl integration would follow
On Wed, Dec 5, 2012 at 2:45 PM, Mary Hinton <m.hin...@nc.rr.com> wrote:
> What is planned for the driver code for Windows?
> Maybe I could help.
> I have a Windows port running and could put more patches in Jira for changes
> to the driver code required by Windows.
> Mary Hinton
> -----Original Message-----
> From: Andrew Stitcher [mailto:astitc...@redhat.com]
> Sent: Wednesday, December 05, 2012 5:04 PM
> To: proton
> Subject: Some proton portability work.
> I've committed some portability work on proton today.
> At this point, proton should configure and compile without error on FreeBSD
> and MacOS X.
> I've also done a bit of work which improves compilation under gcc on Solaris
> too, but this isn't finished (Solaris is missing any functionality to easily
> ignore SIGPIPE when writing to closed sockets).
> I've also done a bit of work to get it cross compile under mingw32, but again
> there are some remaining issues (ignoring the fact that the driver code for
> Windows isn't finished anyway)
> Questions, bugs etc. to me