[jira] [Updated] (PROTON-372) driver does not handle POLLHUP

[ https://issues.apache.org/jira/browse/PROTON-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bozo Dragojevic updated PROTON-372: --- Attachment: 0001-Handle-POLLHUP-as-pending-io.patch This seems like a less heavy-handed

[jira] [Commented] (PROTON-331) session window confuses frames and deliveries

[ https://issues.apache.org/jira/browse/PROTON-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726444#comment-13726444 ] ASF subversion and git services commented on PROTON-331: Commit

[jira] [Resolved] (PROTON-331) session window confuses frames and deliveries

[ https://issues.apache.org/jira/browse/PROTON-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming resolved PROTON-331. Resolution: Fixed Assignee: Rafael H. Schloming session window confuses

[jira] [Resolved] (PROTON-231) Allow messenger to be used inside an event loop

[ https://issues.apache.org/jira/browse/PROTON-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming resolved PROTON-231. Resolution: Fixed Assignee: Rafael H. Schloming I believe the new API

[jira] [Resolved] (PROTON-380) Ruby Message object does not include a body property.

[ https://issues.apache.org/jira/browse/PROTON-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce resolved PROTON-380. - Resolution: Fixed Fix Version/s: 0.5 Ruby Message object does not include a

[jira] [Commented] (PROTON-380) Ruby Message object does not include a body property.

[ https://issues.apache.org/jira/browse/PROTON-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726484#comment-13726484 ] ASF subversion and git services commented on PROTON-380: Commit

Fwd: Build failed in Jenkins: Qpid-proton-j-windows #100

Hey, does anyone know what's up with this build failure? It happened shortly after a commit I made, however according to the stack traces it doesn't seem to be actually getting into any proton code. --Rafael -- Forwarded message -- From: Apache Jenkins Server

proton-j API factory simplification.

Hi folks, I was just thinking perhaps we should simplify all the factory stuff in the proton API. Mostly get rid of it. Don't think it's really needed. Mainly I think we need to make Proton an interface and let folks assign it the desired implementation. Something like: Proton p = new

Re: proton-j API factory simplification.

I like this idea. Right now I'm at a loss to understand what all the factory business is for, and I'm actually pretty familiar with the codebase. I don't think our users stand a snowballs chance in hell of sorting through the myriad of factories, factory impls, service loaders, and service loader

[jira] [Created] (PROTON-382) Perl Message class should expose a Properties attribute

Darryl L. Pierce created PROTON-382: --- Summary: Perl Message class should expose a Properties attribute Key: PROTON-382 URL: https://issues.apache.org/jira/browse/PROTON-382 Project: Qpid Proton

[jira] [Created] (PROTON-383) Perl Message class should expose an Annotations property.

Darryl L. Pierce created PROTON-383: --- Summary: Perl Message class should expose an Annotations property. Key: PROTON-383 URL: https://issues.apache.org/jira/browse/PROTON-383 Project: Qpid Proton

[jira] [Updated] (PROTON-386) Provide Perl post, fetch and mailserver examples

[ https://issues.apache.org/jira/browse/PROTON-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce updated PROTON-386: Description: Provide examples, in Perl, that are feature similar to those in the same