Hi folks, > > If it makes things simpler, perhaps we could focus on a > > working windows client for M3 and get the broker ported for M4? > > Let me see how far I can get today. If the broker won't go, > I'll just update the client patch in the jira issue.
Things are not ready to go. The previous client code has enough problems so it's not really ready to go either. Thank you very much for holding things up for the Windows port, but I'm not comfortable with the state of things to get it done before Andrew gets to work Friday. I apologize for delaying M3. I will continue to work the Windows port on the qpid-port github repo and the interested people can get it from there and continue making progress. If things get stable significantly before M4, I can always make a Windows port kit available more generally. For those interested, here's the status: - the C++ broker starts and deadlocks on a Monitor, but if you restart it in the debugger, it gets past there. - Once past the Monitor thing, it does listen for connections - When a connection arrives, the completion handling is not correctly dispatching back to the acceptor; this dispatching problem is also the root of the client issues (if you're listening, Danny, this is the problem you reported to me... I know what's wrong, but not yet how to fix it). -Steve
