On Sat, Feb 8, 2014 at 12:15 PM, Fraser Adams wrote:
> On 06/02/14 19:59, Rafael Schloming wrote:
>
>> On Tue, Feb 4, 2014 at 3:35 PM, Fraser Adams
>> wrote:
>>
>> It's probably worth aiming for consistency, but TBH I'm an awful lot more
>>> concerned that Proton Messenger doesn't seem to have a
On 06/02/14 19:59, Rafael Schloming wrote:
On Tue, Feb 4, 2014 at 3:35 PM, Fraser Adams
wrote:
It's probably worth aiming for consistency, but TBH I'm an awful lot more
concerned that Proton Messenger doesn't seem to have a mechanism for
setting link configuration and thus I couldn't use it for
On 6 February 2014 22:21, Andrew Stitcher wrote:
> On Thu, 2014-02-06 at 20:36 +0100, Rob Godfrey wrote:
> > ...
> > This bit:
> >
> > TOKEN [IGNORE_CASE] :
> > {
> > < ID : ["a"-"z", "_", "$"] (["a"-"z","0"-"9","_", "$"])* >
> > | < QUOTED_ID : "\"" ( ("\"\"") | ~["\""] )* "\"" >
> > }
On Thu, 2014-02-06 at 20:36 +0100, Rob Godfrey wrote:
> ...
> This bit:
>
> TOKEN [IGNORE_CASE] :
> {
> < ID : ["a"-"z", "_", "$"] (["a"-"z","0"-"9","_", "$"])* >
> | < QUOTED_ID : "\"" ( ("\"\"") | ~["\""] )* "\"" >
> }
>
Cool, thanks for that - does it really have double quote as the
On Tue, Feb 4, 2014 at 3:35 PM, Fraser Adams
wrote:
> So this happens in message.c in
> int pn_message_encode(pn_message_t *msg, char *bytes, size_t *size)
>
> ..
>
> err = pn_data_fill(msg->data, "DL[CzSSSCssttSIS]", PROPERTIES,
> msg->id,
> pn_stri
On 6 February 2014 18:14, Andrew Stitcher wrote:
> On Thu, 2014-02-06 at 12:57 +, Gordon Sim wrote:
> > On 02/06/2014 12:49 PM, Rob Godfrey wrote:
> > > SQL would use double quotes around identifiers that would otherwise
> > > conflict with keywords, etc... (As an added benefit the Java Broke
On 06/02/14 17:14, Andrew Stitcher wrote:
On Thu, 2014-02-06 at 12:57 +, Gordon Sim wrote:
On 02/06/2014 12:49 PM, Rob Godfrey wrote:
SQL would use double quotes around identifiers that would otherwise
conflict with keywords, etc... (As an added benefit the Java Broker already
copes with th
On Thu, 2014-02-06 at 12:57 +, Gordon Sim wrote:
> On 02/06/2014 12:49 PM, Rob Godfrey wrote:
> > SQL would use double quotes around identifiers that would otherwise
> > conflict with keywords, etc... (As an added benefit the Java Broker already
> > copes with this syntax :-) )...
>
> That wou
On 02/06/2014 12:49 PM, Rob Godfrey wrote:
SQL would use double quotes around identifiers that would otherwise
conflict with keywords, etc... (As an added benefit the Java Broker already
copes with this syntax :-) )...
That would get my vote!
---
On 6 February 2014 12:10, Gordon Sim wrote:
> On 02/04/2014 07:56 PM, Fraser Adams wrote:
>
>> On 03/02/14 21:08, Gordon Sim wrote:
>>
>>> Listing the incoming and outgoing entities is useful even for a
>>> standalone broker. Creating them offers a mechanism similar to the
>>> links/bridges in 0-
On 02/04/2014 07:56 PM, Fraser Adams wrote:
On 03/02/14 21:08, Gordon Sim wrote:
Listing the incoming and outgoing entities is useful even for a
standalone broker. Creating them offers a mechanism similar to the
links/bridges in 0-10.
Yeah I can see why listing the incoming/outgoing entities w
On 03/02/14 23:31, Robbie Gemmell wrote:
More of an observation/question for all, than reply to youFraser I
noted the following while I was skimming:
" These sends resulted in the following messages from drain:
1. From Proton Messenger send:
Message(properties={x-amqp-absolute-expiry-time:
On 03/02/14 23:20, Robbie Gemmell wrote:
So, erm, yeah...gawp...thought about book writing Fraser? ;)
Yeah it turned out to be longer than I was expecting, it wasn't until I
saw it printed off that I realised how much there was of it, I was
clearly having *way* too much fun :->
I do hope that
Thanks again for another update Gordon. Some responses inline below.
On 03/02/14 21:08, Gordon Sim wrote:
On 02/03/2014 07:53 PM, Fraser Adams wrote:
On 03/02/14 15:38, Gordon Sim wrote:
They should be set for outgoing messages as of 0.24[1]. What version
were you using?
I was actually using
On Mon, 2014-02-03 at 21:08 +, Gordon Sim wrote:
> ...
> [...]
> >> However we could probably look at ways to (optionally?) make this more
> >> lenient. It certainly is also something that should be highlighted
> >> more prominently in documentation somehow.
> > It would be *really really good*
More of an observation/question for all, than reply to youFraser I
noted the following while I was skimming:
" These sends resulted in the following messages from drain:
1. From Proton Messenger send:
Message(properties={x-amqp-absolute-expiry-time:0, x-amqp-creation-time:0,
x-amqp-group-seq
So, erm, yeah...gawp...thought about book writing Fraser? ;)
On 3 February 2014 19:53, Fraser Adams wrote:
> On 03/02/14 15:38, Gordon Sim wrote:
>
>>
>> Although AMQP itself does not place any restrictions on application
>> property names, the selector syntax for AMQP 1.0 is that of JMS
>> selec
On 02/03/2014 07:53 PM, Fraser Adams wrote:
On 03/02/14 15:38, Gordon Sim wrote:
They should be set for outgoing messages as of 0.24[1]. What version
were you using?
I was actually using 0.27 off trunk built a couple of weeks ago.
Which properties didn't work for you using the x-amqp-* name?
On 03/02/14 15:38, Gordon Sim wrote:
Thanks for taking the time to write this up and share it with the
list! Feedback from users is what drives everything forward.
No worries, I've been meaning to find the time to properly explore the
AMQP 1.0 capabilities for ages. Part of my problem has been
On 02/02/2014 09:24 PM, Fraser Adams wrote:
Hello all,
Over the last couple of weekends I decided to make a concerted effort to
try and get my head around the Qpid AMQP 1.0 support and to see if I can
replicate a whole bunch of use cases that I was able to support in AMQP
0.10.
I've attached a w
Hello all,
Over the last couple of weekends I decided to make a concerted effort to
try and get my head around the Qpid AMQP 1.0 support and to see if I can
replicate a whole bunch of use cases that I was able to support in AMQP
0.10.
I've attached a write up of my experiments along with some
21 matches
Mail list logo
