Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (nike.apache.org: domain of marnie.mccormack@googlemail.com
 designates 64.233.182.185 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=sCaeteFtWx4ykMKr69iqRz5bGuQH4nsp8zxD5W4Cd1z4y4L21pPvT0vjIc5mmFnhI0
         ZdJAadMpamAXbIfSjYdZ5XlbAPpLcD7ErLjJZlWGulNZPUF0VABq3LpnY1VnKx73S3Qa
         5JKev2Q+hCr9bBKdTQCzMlq4MU4jC4tEYUG+E=
MIME-Version: 1.0
In-Reply-To: <497E781B.5090505@redhat.com>
References: <1232758751329-2207029.post@n2.nabble.com>
	 <497B3287.1000101@redhat.com>
	 <b9472b590901260147q5d57b24fm7d5de764db1ea29@mail.gmail.com>
	 <1233024765631-2222111.post@n2.nabble.com>
	 <497E781B.5090505@redhat.com>
Date: Tue, 27 Jan 2009 10:11:31 +0000
Message-ID: <b9472b590901270211u1839bb7hb3233a5a0555ac19@mail.gmail.com>
Subject: Re: qpid broker on windows
From: Marnie McCormack <marnie.mccormack@googlemail.com>
To: users@qpid.apache.org, cctrieloff@redhat.com
Content-Type: multipart/alternative; boundary=0015174bf0f84eca8a046174140d

--0015174bf0f84eca8a046174140d
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

The Java broker works with the Java Client and the 0-8 .Net client. It does
not yet support 0-10 features, but if you're using JMS that's probably not a
major issue.

Marnie

On Tue, Jan 27, 2009 at 2:57 AM, Carl Trieloff <cctrieloff@redhat.com>wrote:

>
> you are correct, the Java broker is not up to 0-10 yet.
> Carl.
>
>
>
> falconair wrote:
>
>> I stopped using the Java broker months ago because the latest clients
>> (java,
>> .NET) are based on version 0-10 protocol and the only broker which
>> supports
>> this version is c++.  Am I wrong in my assumption?  If Java broker works
>> with m4 clients, I'm happy to switch to java for dev/test work.
>>
>>
>>
>> Marnie McCormack wrote:
>>
>>
>>> Hi,
>>>
>>> I thought it'd be useful to point out that the Qpid Java Broker comes
>>> complete with a Windows startup .bat and is widely used by developers on
>>> Windows, out of the box so to speak. It is production proven.
>>> You can find out what you need to get started with the Java Broker at:
>>> http://qpid.apache.org/getting-started-guide.html
>>>
>>> Please give us a shout if you need any extra info.
>>>
>>> Regards,
>>> Marnie
>>> On Sat, Jan 24, 2009 at 3:23 PM, Carl Trieloff
>>> <cctrieloff@redhat.com>wrote:
>>>
>>>
>>>
>>>> falconair wrote:
>>>>
>>>>
>>>>
>>>>> Another poster asked for a pre-built windows binary of qpid broker.
>>>>>  I'd
>>>>> like
>>>>> to encourage the devs to provide it as well.
>>>>> Since qpid is still not very well known, I suspect it is the
>>>>> down-in-the-trenches developers who are introducing qpid to their
>>>>> companies. Almost every place I have worked, developer workstations are
>>>>> windows based. In other words, devs are unlikely to experiment with
>>>>> qpid
>>>>> if
>>>>> they have to
>>>>> track down a fairly large number of dependencies and compile from
>>>>> source.
>>>>> The problem is worse in distributed environments where one dev either
>>>>> has to
>>>>> distributed his own qpid exe or convince other devs to build it from
>>>>> scratch.
>>>>>
>>>>> I think this problem will be mitigated by amqp 0-10 java broker, but
>>>>> until
>>>>> then, pre-built binaries will be very useful.
>>>>>
>>>>>
>>>>>
>>>>>
>>>> yes, we have started a thread on the dev list to this end, and a version
>>>> has been built for Windows. Once
>>>> a few people have validated it, we can post it to the user list.
>>>>
>>>> If you want to help validate the build, jump on the dev list.
>>>>
>>>> Carl.
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> Apache Qpid - AMQP Messaging Implementation
>>>> Project:      http://qpid.apache.org
>>>> Use/Interact: mailto:users-subscribe@qpid.apache.org
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
>

--0015174bf0f84eca8a046174140d--