Re: arguments vs. params (was Re: Bogus debug information?)

Joshua Kramer wrote: I am not sure why you need the arguments fieldtable It can be added to the params for the fields that you want to match on. see how I build them in Thank you Carl. I was under the impression that parameters passed via params were constrained to the valid parameters

arguments vs. params (was Re: Bogus debug information?)

I am not sure why you need the arguments fieldtable It can be added to the params for the fields that you want to match on. see how I build them in Thank you Carl. I was under the impression that parameters passed via params were constrained to the valid parameters present in a particula

Re: [c++]: Sketch of a high-level, protocol independent API

Gordon, One comment I would have. In AMQP 1.0 we will have Queues and links, which can still handle the 0-10 model. However in an API would we not want to drop the noun Exchange and just use BindTo() or LinkTo() so that the API will work forwards to AMQP 1.0 with naming? Carl. Gordon Sim

[jira] Resolved: (QPID-1762) java client blows up when it gets a mime type it doesn't recognize

[ https://issues.apache.org/jira/browse/QPID-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming resolved QPID-1762. --- Resolution: Fixed > java client blows up when it gets a mime type it doesn't recognize

[jira] Resolved: (QPID-1761) BBEncoder.grow doesn't properly copy and ends up garbling the encoded data

[ https://issues.apache.org/jira/browse/QPID-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming resolved QPID-1761. --- Resolution: Fixed > BBEncoder.grow doesn't properly copy and ends up garbling the enco

Re: Bogus debug information?

Joshua Kramer wrote: Hello, In order to solve this problem, I tried adjusting the order of parameters. Specifically, I put the 'const framing::FieldTable &arguments' as the first parameter to the authorise() methods. Still no dice - the function call is jumping to the incorrect authorise.

[jira] Commented: (QPID-1807) Backout Flow to Disk from 0.5 to allow more time for testing

[ https://issues.apache.org/jira/browse/QPID-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698372#action_12698372 ] Martin Ritchie commented on QPID-1807: -- The merged file do seem to maintain better info

[jira] Assigned: (QPID-1807) Backout Flow to Disk from 0.5 to allow more time for testing

[ https://issues.apache.org/jira/browse/QPID-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie reassigned QPID-1807: Assignee: Martin Ritchie > Backout Flow to Disk from 0.5 to allow more time for testing > -

[jira] Created: (QPID-1807) Backout Flow to Disk from 0.5 to allow more time for testing

Backout Flow to Disk from 0.5 to allow more time for testing - Key: QPID-1807 URL: https://issues.apache.org/jira/browse/QPID-1807 Project: Qpid Issue Type: Task Componen

Re: [0.5][README] Upcoming SVN surgery

2009/4/10 Aidan Skinner : > This is a "watch your head, incoming svn surgery" email. Sorry. > > The Java server is currently the long sticking out thing that's > holding up 0.5, and there's significant enough concern about some of > the changes that have gone in that it's probably best to revert th