activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dejan Bosanac <de...@nighttale.net>
Subject Re: ActiveMQ - HTTP - Remoting
Date Thu, 29 Oct 2009 09:49:33 GMT
Hi Charles,

http transport should work just like a regular tcp transport. The only thing
is that it is slower, since messages are encoded to xml when they're on the
wire.

Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net


On Thu, Oct 29, 2009 at 10:08 AM, cmoulliard <cmoulliard@gmail.com> wrote:

>
> Does it make sense to design a topology like this between different
> osgi servers to propose remote services though an ActiveMq queue playing
> the
> role of osgi server integrator ?
>
> 1) Bundle A
>
> This bundle contains a spring DSL xml file with routes defined like this :
>
> from().
> .to()
> .to()
> .to(ActiveMq:queueOut)
>
> and service waiting feedback
>
> from(ActiveMq:queueIn).
> .to()
>
> deployed on server OSGI (1)
>
> 2) Bundle B
>
> from(ActiveMq:queueOut).
> .to() // Service replying to the request
> .to(ActiveMq:queueIn)
>
> deployed in server OSGI (2)
>
> Additional question :
>
> Are there any restrictions if we use HTTP transport connector of ActiveMq
> to
> place Java object on the queue (size, serialization, ....) ?
>
> Regards,
>
> -----
> Charles Moulliard
> SOA Architect
>
> My Blog :  http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/
> --
> View this message in context:
> http://www.nabble.com/ActiveMQ---HTTP---Remoting-tp26109373p26109373.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message