[
https://issues.apache.org/jira/browse/PROTON-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726885#comment-13726885
]
ASF subversion and git services commented on PROTON-369:
Commit 15
Having had to dig a bit more into the Java code base over the past few
weeks I've noticed some packaging/organizational issues. In particular I
found it difficult to figure out where to look for any given java file as
there doesn't seem to be much rhyme or reason to how classes are split up
between
[
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 examp
Darryl L. Pierce created PROTON-386:
---
Summary: Provide Perl post, fetch and mailserver examples
Key: PROTON-386
URL: https://issues.apache.org/jira/browse/PROTON-386
Project: Qpid Proton
Is
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
Darryl L. Pierce created PROTON-385:
---
Summary: Perl Message class should expose an Body property.
Key: PROTON-385
URL: https://issues.apache.org/jira/browse/PROTON-385
Project: Qpid Proton
Darryl L. Pierce created PROTON-384:
---
Summary: Perl Message class should expose an Instructions property.
Key: PROTON-384
URL: https://issues.apache.org/jira/browse/PROTON-384
Project: Qpid Proton
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
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 i
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 ProtonJ
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
Date: Thu, Aug 1, 20
[
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
[
https://issues.apache.org/jira/browse/PROTON-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726484#comment-13726484
]
ASF subversion and git services commented on PROTON-380:
Commit 15
[
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 improve
[
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
[
https://issues.apache.org/jira/browse/PROTON-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726444#comment-13726444
]
ASF subversion and git services commented on PROTON-331:
Commit 15
[
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 appro
17 matches
Mail list logo
