On Sat, Sep 25, 2010 at 12:33 AM, William Henry <[email protected]> wrote:
> I would think that an ESB might be a bit overkill here. There ought to be a > lighter-weight solution. > +1, but if you have more and more requirements like this which is not directly related to what we are doing in Qpid ESB would be a good solution for the futuree. Lahiru > > Also with the new API I think it might be easier to provide a REST > "wrapper". The URL might map pretty easily to a node and the REST semantics > would sit nicely on top of sends and fetches. No? > > William > > ----- "Lahiru Gunathilake" <[email protected]> wrote: > > > Hi Clive, > > > > I am not sure about this feature in Qpid. > > > > You can simply use an ESB infront of Qpid and configure ESB to send > > the > > message to Qpid instance .. so you have to directly talk to the proxy > > in > > your ESB When you are talking to the ESB instance you can invoke as > > you like > > (SOAP,REST,JMS any transport). > > > > Lahiru > > > > On Fri, Sep 24, 2010 at 10:24 PM, Clive Lilley <[email protected]> > > wrote: > > > > > Hi, > > > > > > Been using QPID for a while and it is performing very well . > > > > > > My client has asked me to look at how easy it might be to produce a > > RESTful > > > interface to QPID, so that data can be sent/received using URL's and > > the > > > http PUT/GET operations. > > > > > > Has anyone tried this before with QPID? > > > > > > Clive. > > > > > > > > --------------------------------------------------------------------- > > > Apache Qpid - AMQP Messaging Implementation > > > Project: http://qpid.apache.org > > > Use/Interact: mailto:[email protected] > > > > > > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > >
