On 21/03/13 13:19, Ken Giusti wrote:
I'd rather see a single "top level" broker configuration command that
supports all the configuration aspects of the broker. Openssl and NSS (certutil) take
this approach. I think it would tend towards unifying the configuration experience
(e.g. naming
Hi,
How can I tell qpid-send to use specific content type? I need to set content
type to "text/plain" so on receiving end the Java JMS client will get
javax.jms.TextMessage instead of javax.jms.BytesMessage.
Kind regards, Jan
Jan Bareš
Calypso Lead Developer
In association with
WOOD & Company
- Original Message -
> From: "Gordon Sim"
> To: users@qpid.apache.org
> Sent: Thursday, March 21, 2013 11:47:38 AM
> Subject: Re: [c++]: Progressing AMQP 1.0 support for 0.22 release
>
> On 03/21/2013 01:19 PM, Ken Giusti wrote:
> > H... seems like there's not a strong opinion either
On 03/21/2013 01:19 PM, Ken Giusti wrote:
H... seems like there's not a strong opinion either way.
On reflection, I think I'm actually fine with your original proposal
(separate tool - very generic management tool). As a developer, this
tool would really come in handy - it allows me to mana
H... seems like there's not a strong opinion either way.
On reflection, I think I'm actually fine with your original proposal (separate
tool - very generic management tool). As a developer, this tool would really
come in handy - it allows me to manage newly developed objects without the nee
