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
 66.249.92.169 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:x-google-sender-auth;
        b=T368tzT1FJZN2znB6HbtQK+y77RKKM1na2BvJ7YE4Vh+3tc3x8aZHv7nYKMPnZ9oFPF6PnhJWjqqmoxiUgHy794Hh//Q2XttVl21KA/xhrPA5DAkAMWcVaq9eNbJDyWZAN+4izH4HdvSAD03k2NWb3aMF8Ye3iLiyP1ZnKGAwc0=
Message-ID: <af2843cd0606210732s25f02d56r89d82bf6cb49e2b9@mail.gmail.com>
Date: Wed, 21 Jun 2006 10:32:19 -0400
From: "Hiram Chirino" <hiram@hiramchirino.com>
Sender: chirino@gmail.com
To: activemq-dev@geronimo.apache.org
Subject: Re: AMQP
In-Reply-To: <46E05001-B8E9-44CB-A4FC-2FC168F0C416@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <46E05001-B8E9-44CB-A4FC-2FC168F0C416@gmail.com>

+1 !  BTW IMO the spec is still fuzzy.  I think they need to clarify
it a bit more.  But I think it's something we should be able to
implement really easy.

On 6/20/06, Brian McCallister <brian.mccallister@gmail.com> wrote:
> FYI: http://www.infoq.com/news/amq
>
> AMQP looks to be an attempt at wire protocol specification like
> openwire or stomp.
>
> Probably good for us to look at, though the licensing probably needs
> to bounce through licensing@a.o before we do much as it is not
> immediately clear if it is okay. I probably is, but I'd love to get
> Cliff's opinion.
>
> -Brian
>


-- 
Regards,
Hiram

Blog: http://hiramchirino.com