On Wed, Nov 14, 2012 at 10:36 PM, Ted Ross wrote:
>
> On 11/14/2012 12:56 PM, Rafael Schloming wrote:
>
>> On Wed, Nov 14, 2012 at 6:37 PM, Ted Ross wrote:
>>
>> On 11/14/2012 11:49 AM, Rafael Schloming wrote:
>>>
>>> How does the packaging prevent this?
1) Develop the non-b
William Henry created PROTON-137:
Summary: pn_messenger_incoming_subscription returning null
Key: PROTON-137
URL: https://issues.apache.org/jira/browse/PROTON-137
Project: Qpid Proton
Issue T
On 11/14/2012 12:56 PM, Rafael Schloming wrote:
On Wed, Nov 14, 2012 at 6:37 PM, Ted Ross wrote:
On 11/14/2012 11:49 AM, Rafael Schloming wrote:
How does the packaging prevent this?
1) Develop the non-blocking aspects of the API. This might just
involve a
few additions to the current
[
https://issues.apache.org/jira/browse/PROTON-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497407#comment-13497407
]
Ken Giusti commented on PROTON-111:
---
Added idle timeout to the proton-c implementation:
[
https://issues.apache.org/jira/browse/PROTON-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti updated PROTON-111:
--
Component/s: (was: proton-c)
> Support an idle time-out threshold.
> --
[
https://issues.apache.org/jira/browse/PROTON-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming updated PROTON-136:
---
Assignee: Ken Giusti
> Add support for SSL session resumption
> -
Affan Dar created PROTON-136:
Summary: Add support for SSL session resumption
Key: PROTON-136
URL: https://issues.apache.org/jira/browse/PROTON-136
Project: Qpid Proton
Issue Type: New Feature
Yeah, sorry, I was racing to get the 0.2 release out. I figured you'd
rather have it undocumented than not have it at all. ;-)
--Rafael
On Wed, Nov 14, 2012 at 7:57 PM, William Henry wrote:
>
>
> - Original Message -
> > On Wed, Nov 14, 2012 at 7:31 PM, William Henry
> > wrote:
> >
> >
- Original Message -
> On Wed, Nov 14, 2012 at 7:31 PM, William Henry
> wrote:
>
> > I would like to reopen Proton-46. I see the changes made to
> > Messenger but
> > it is unclear how this can be of any value unless you can get at
> > what
> > subscription an incoming message is associ
On Wed, Nov 14, 2012 at 7:31 PM, William Henry wrote:
> I would like to reopen Proton-46. I see the changes made to Messenger but
> it is unclear how this can be of any value unless you can get at what
> subscription an incoming message is associated with.
>
>
> Perhaps all that is needed is an e
I would like to reopen Proton-46. I see the changes made to Messenger but it is
unclear how this can be of any value unless you can get at what subscription an
incoming message is associated with.
Perhaps all that is needed is an explanation of what was "fixed" when it was
closed. Or perhaps
[
https://issues.apache.org/jira/browse/PROTON-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497291#comment-13497291
]
Rafael H. Schloming commented on PROTON-134:
I believe Ken had a fix for this
On Wed, Nov 14, 2012 at 6:37 PM, Ted Ross wrote:
>
> On 11/14/2012 11:49 AM, Rafael Schloming wrote:
>
>>
>> How does the packaging prevent this?
>>
>>
>>1) Develop the non-blocking aspects of the API. This might just
>> involve a
>> few additions to the current API or possibly adding a disti
On 11/14/2012 11:49 AM, Rafael Schloming wrote:
How does the packaging prevent this?
1) Develop the non-blocking aspects of the API. This might just involve a
few additions to the current API or possibly adding a distinct non-blocking
API which would be a layer underneath the current API.
On 11/14/2012 12:24 PM, Andrew Stitcher wrote:
On Wed, 2012-11-14 at 17:49 +0100, Rafael Schloming wrote:
...
How does the packaging prevent this?
Not to put words in Ted's mouth, but I think what he is talking about
here is that the messenger API code itself depends on the driver code.
Andre
On Wed, 2012-11-14 at 17:49 +0100, Rafael Schloming wrote:
> ...
> How does the packaging prevent this?
Not to put words in Ted's mouth, but I think what he is talking about
here is that the messenger API code itself depends on the driver code.
Andrew
On Wed, Nov 14, 2012 at 4:54 PM, Ted Ross wrote:
> One of the problems we've had for a long time with wrapped bindings is the
> mismatch of threading models. For example, a Ruby program using an
> extension module written in C/C++ will hang if a call into the extension
> blocks. This is because
On Wed, Nov 14, 2012 at 10:54:45AM -0500, Ted Ross wrote:
> One of the problems we've had for a long time with wrapped bindings
> is the mismatch of threading models. For example, a Ruby program
> using an extension module written in C/C++ will hang if a call into
> the extension blocks. This is
[
https://issues.apache.org/jira/browse/PROTON-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497204#comment-13497204
]
Rafael H. Schloming commented on PROTON-135:
Are there specific scenarios you'
Ted Ross created PROTON-135:
---
Summary: Provide hooks in proton-c to allow override of
malloc/free for internal types
Key: PROTON-135
URL: https://issues.apache.org/jira/browse/PROTON-135
Project: Qpid Proto
[
https://issues.apache.org/jira/browse/PROTON-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned PROTON-134:
---
Assignee: Ted Ross
> pn_connector makes a blocking call to socket::connect
>
One of the problems we've had for a long time with wrapped bindings is
the mismatch of threading models. For example, a Ruby program using an
extension module written in C/C++ will hang if a call into the extension
blocks. This is because the extension uses pthreads and the host
program uses
On Wed, 2012-11-14 at 09:19 -0500, Mary Hinton wrote:
> ...
> I'd like to share the status of the Windows port of the proton code.
> ...
> In the meantime, I would like to have a public place to put the port so that
> others can join in with the Windows version.
>
> What is the best way to do thi
Hi everyone,
I'd like to share the status of the Windows port of the proton code.
The last rebase of the proton dll codebase was this Saturday, Nov. 10th.
I haven't updated to the latest python tests yet, but currently, the port is
running and passing most of the python tests.
Totals:
[
https://issues.apache.org/jira/browse/PROTON-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey reassigned PROTON-133:
--
Assignee: Rob Godfrey
> 2 Flow frames sent per receiver message settled /w a disposition.
>
[
https://issues.apache.org/jira/browse/PROTON-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey resolved PROTON-133.
Resolution: Fixed
Fix Version/s: 0.3
patch applied
> 2 Flow frames sent per
Ted Ross created PROTON-134:
---
Summary: pn_connector makes a blocking call to socket::connect
Key: PROTON-134
URL: https://issues.apache.org/jira/browse/PROTON-134
Project: Qpid Proton
Issue Type: B
27 matches
Mail list logo