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 spaace@gmail.com designates
 209.85.146.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=N0kdR+mh7Pr0TTG+ujN2sEoGWLOd2avXupVuiTpoB2ZkJm+7sNp5veVnrH+TnkXwiD
         s0fOMmQGzLL0E/5s20OENmpNj1W8zwbYktg2j4od0ejuE1aNUorqzS87iZaaplE7atnW
         YSQRtOI2ZDqdkmPSXr1K+cr/n1Jao8iYUkHdw=
MIME-Version: 1.0
Date: Thu, 29 Jan 2009 14:24:29 +0530
Message-ID: <a582b900901290054g5d34ceafk2114588435bad9b0@mail.gmail.com>
Subject: RE: qpid broker on windows
From: spaace <spaace@gmail.com>
To: users@qpid.apache.org
Content-Type: multipart/alternative; boundary=00163649a73d7af21604619b3c66

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

Hi,

I'm new to Qpid and have been following the threads and reading up on the
docs for some time. I'm trying to decide on the brokers to be used for a
private project and have this doubt.

Why are multiple brokers that bring with them additional compatibility
requirements being developed by QPID ? Is it for enhancing the reach to
other platforms that only a particular technology might support (JMS etc) or
is this a corporate missive from Redhat or some one else?

Where can i find the information regarding ways in which the brokers differ
from one another ?

Regards
Arun

-----Original Message-----
From: Marnie McCormack [mailto:    ]
Sent: Thursday, January 29, 2009 2:02 PM
To: users@qpid.apache.org
Subject: Re: qpid broker on windows

See what you mean, thanks.

The Qpid roadmap shows 0-10 implementation on the Java broker as one of our
next big ticket deliveries. This would mean that the C++ client could again
interop with the Java broker.

On the C# front, we are discussing on the dev list the strategic solution
going forward, but again 0-10 implementation on the Java broker will put the
choice of .Net client in the user's hands.

Appreciate this doesn't help now, but just for info !

Regards,
Marnie

On Thu, Jan 29, 2009 at 6:41 AM, falconair <shahbazc@gmail.com> wrote:

>
> Some components of my system need to interact with the broker through
> C# (and soon C++).  That is the main motivation behind using qpid,
> rather than other jms providers.
>
>
> Marnie McCormack wrote:
> >
> > The Java broker works with the M4 Java Client and the M4 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
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://n2.nabble.com/qpid-broker-on-windows-tp2207029p2237421.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
>  Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>

Internal Virus Database is out of date.
Checked by AVG - http://www.avg.com
Version: 8.0.176 / Virus Database: 270.10.13/1912 - Release Date: 1/23/2009
6:54 PM

--00163649a73d7af21604619b3c66--