You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by myprasanna <my...@gmail.com> on 2011/01/16 00:27:14 UTC
a top website with millions of page views migrating from morbidq
restq to activemq
hey guys,
we are migrating from:
www.morbidq.com/trac/wiki/RestQ
to activemq. we would like to keep the interfacing intact, and want to know
where to extend activemq so that we can maintain all the application logic
at a web-server. for those unfamiliar with restq, it allows you to receive
web-callbacks for 5 simple events: connect, disconnect, subscribe,
unsubscribe, send_message; and the web-server can determine if any of these
have to be allowed or not.
what we want to do now is to extend activemq so that we continue to receive
these callbacks. if we can write the extensions in ruby, that's most
preferred, but java is OK, if it's going to be a simple set of calls. any
high level guidance as to how to achieve this is highly appreciated. it
seems like i have to extend a bunch of classes if i'm not wrong?
cheers,
-prasanna
--
View this message in context: http://activemq.2283324.n4.nabble.com/a-top-website-with-millions-of-page-views-migrating-from-morbidq-restq-to-activemq-tp3219583p3219583.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: a top website with millions of page views migrating from morbidq
restq to activemq
Posted by Dejan Bosanac <de...@nighttale.net>.
Hi Prasanna,
I'd suggest use of Apache Camel (http://camel.apache.org) to do this
bridge between broker and the http server
Regards
--
Dejan Bosanac
-----------------
FuseSource - The experts in open source integration and messaging.
Email: dejanb@fusesource.com
Web: http://fusesource.com
Twitter: http://twitter.com/dejanb
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Sun, Jan 16, 2011 at 12:27 AM, myprasanna <my...@gmail.com> wrote:
>
> hey guys,
>
> we are migrating from:
>
> www.morbidq.com/trac/wiki/RestQ
>
> to activemq. we would like to keep the interfacing intact, and want to know
> where to extend activemq so that we can maintain all the application logic
> at a web-server. for those unfamiliar with restq, it allows you to receive
> web-callbacks for 5 simple events: connect, disconnect, subscribe,
> unsubscribe, send_message; and the web-server can determine if any of these
> have to be allowed or not.
>
> what we want to do now is to extend activemq so that we continue to receive
> these callbacks. if we can write the extensions in ruby, that's most
> preferred, but java is OK, if it's going to be a simple set of calls. any
> high level guidance as to how to achieve this is highly appreciated. it
> seems like i have to extend a bunch of classes if i'm not wrong?
>
> cheers,
> -prasanna
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/a-top-website-with-millions-of-page-views-migrating-from-morbidq-restq-to-activemq-tp3219583p3219583.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>