Mailing-List: contact activemq-dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of chirino@gmail.com designates
 64.233.184.192 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Lw5OVgE1xsOzrWDOcnEvx2jCOmOEGpTFsfErruRqL9JOj2dnpAIZq7AEUABYzpP9U53vCYoTjR+wx0z0TFtzT0Lbjx7+2wdqZNquW4Up4zr1/mFLr6WcJ8qwVpLFm6WGaaKW067M+Ww6fpgfC5mJFF+8pFA0ReXdSlSpIsCKFoA=
Message-ID: <af2843cd0603160445s32870d96x312bf62dfc3332fd@mail.gmail.com>
Date: Thu, 16 Mar 2006 07:45:55 -0500
From: "Hiram Chirino" <hiram@hiramchirino.com>
Sender: chirino@gmail.com
To: activemq-dev@geronimo.apache.org
Subject: Re: OpenWire tight/loose encoding
In-Reply-To: 
 <221951ED658AA34D935E2B5FB6934920CB202F@stosrv-exchange.portwise.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: 
 <221951ED658AA34D935E2B5FB6934920CB202F@stosrv-exchange.portwise.com>

Hi Mats!

On 3/16/06, Mats Forsl=F6f <Mats.Forslof@portwise.com> wrote:
> Hi,
>
> We need some additional information on the OpenWire protocol to wrap up o=
ur work on the C++ AMQ client.
>
> 1. To use loose encoding what do we have to do, is it simply to set the t=
ight encoding attribute to false on the OpenWireFormat package and then sen=
d each package attributes one after each other?
>

OpenWire should always start up in loose encoding mode, in version 1
of the protocol, with all options off by default.  This ensures
backward compatibitlity since future clients will beforced to be
backward compatible to even start talking.  The clients then exchange
a WireFormatInfo which contains information about the highest version
of the protocol and requested protocol options that should be turned
on.  After that exchange both sides can upgrade the version and
options to a set that is compatible between the 2 ends.

> 2. What determines the order of the attributes on each package? The order=
 now seems to be determined by the groovy scripts.

They are in the order that they were defined in the orifinal Java
command classes.  The groovy script just preserves the order.

>
> 3. What about the order of the boolean flags used in tight encoding, what=
 does each position stand for?
>

The bits in the BooleanStream are also serialized in the same order.

> I must ask you of some documentation on this because we cannot verify tha=
t our code is correct otherwise.
>

Any time!  I guess we need to update the C++ guy to support loose
encoding since that is now the minimum requirement.  At least it's
much simpler to implement.  Should I work on that or have you guys
allready have that covered?

Regards,
Hiram

> Please help!
>
> Regards,
> Mats Forsl=F6f
>


--
Regards,
Hiram