Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (athena.apache.org: domain of fraser.adams@blueyonder.co.uk
 designates 81.103.221.48 as permitted sender)
Message-ID: <4E8EF9DD.7040100@blueyonder.co.uk>
Date: Fri, 07 Oct 2011 14:08:45 +0100
From: Fraser Adams <fraser.adams@blueyonder.co.uk>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: users@qpid.apache.org
Subject: Re: How to set a binding on a receiver
References: <4E8C1629.4060206@list-group.com> <4E8C3164.8010308@redhat.com>
 <4E8ECADF.3040205@blueyonder.co.uk> <4E8EF3DA.4020600@redhat.com>
In-Reply-To: <4E8EF3DA.4020600@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


> I guess it depends on how you interpret 'directly'. What I meant was 
> that the API does not support modifying the bindings or other address 
> properties for a receiver once it is created.
>
I expect that my interpretation of the term "API" is "looser" than yours :-)

I guess that I (in my head at any rate) look on the address options as 
part of the messaging API 'cause that's the only way to set many things 
that were once explicit method calls in the client API.

Frase

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org