Re: Small proton (mostly build) issues

Hi Andrew, - Original Message - Ken, When you added Openssl support to proton was there a specific reason you detected it by hand rather than using cmake FindPackage? Also HAVE_OPENSSL_H isn't used anywhere. The only reason would be cmake ignorance :) I attach attach a

[jira] [Commented] (PROTON-40) Batching of message IDs in Disposition frames not supported

[ https://issues.apache.org/jira/browse/PROTON-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13466808#comment-13466808 ] Ted Ross commented on PROTON-40: I've lowered the priority of this issue to minor. There's

[jira] [Created] (PROTON-41) Transport tests failing against Proton-j

Rob Godfrey created PROTON-41: - Summary: Transport tests failing against Proton-j Key: PROTON-41 URL: https://issues.apache.org/jira/browse/PROTON-41 Project: Qpid Proton Issue Type: Bug

[jira] [Resolved] (PROTON-41) Transport tests failing against Proton-j

[ https://issues.apache.org/jira/browse/PROTON-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-41. --- Resolution: Fixed Transport tests failing against Proton-j

[jira] [Commented] (PROTON-38) SSL will enter infinite loop should socket prematurely close.

[ https://issues.apache.org/jira/browse/PROTON-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13466894#comment-13466894 ] Ken Giusti commented on PROTON-38: -- Found another infinite loop while testing against the

Re: proton port to windows using Visual Studio 2010 tools

Hi Mary, Welcome to the list! I'm looking forward to seeing the issues you've hit. It would be great to have proton working with the Visual Studio toolset. If you have patches ready to go already our main tools for collaboration are JIRA[1] and reviewboard[2]. Please feel free to ask questions

Re: Small proton (mostly build) issues

On Fri, Sep 28, 2012 at 6:02 PM, Andrew Stitcher astitc...@redhat.comwrote: Ken, When you added Openssl support to proton was there a specific reason you detected it by hand rather than using cmake FindPackage? Also HAVE_OPENSSL_H isn't used anywhere. I attach attach a patch to neaten this

RE: proton port to windows using Visual Studio 2010 tools

Thanks, I downloaded the latest code on Saturday and merged what I had. I changed code in 26 files. Some of the changes will be easy to incorporate into the current codebase, others will need decisions from the group as to the best way to add the Windows changes (e.g. #ifdef (s) and/or separate

Re: proton port to windows using Visual Studio 2010 tools

Hi Mary, Welcome to proton development! Regarding your pipe issue, please see the pn_socket_pair function in the QPID-4181 patch. I think you can use that with WSAPoll, but if the implementation in driver.c with select() is easier to just copy, you might as well use that. Use of WSAPoll or

[jira] [Commented] (PROTON-42) Maven supriously reporting failure against unit tests

[ https://issues.apache.org/jira/browse/PROTON-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13467144#comment-13467144 ] Hiram Chirino commented on PROTON-42: - This patch should fix that:

[jira] [Created] (PROTON-43) Provides messenger send/receive examples in C

Darryl L. Pierce created PROTON-43: -- Summary: Provides messenger send/receive examples in C Key: PROTON-43 URL: https://issues.apache.org/jira/browse/PROTON-43 Project: Qpid Proton Issue

[jira] [Resolved] (PROTON-42) Maven supriously reporting failure against unit tests

[ https://issues.apache.org/jira/browse/PROTON-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-42. --- Resolution: Fixed Patch applied (magically before it was even posted ;-) ) Maven