| Author |
Message |
|
| tonyg |
 Posted: Sat Feb 02, 2008 12:14 am |
 |
|
|
User
Joined: 07 Nov 2006
Posts: 199
|
|
| Back to top |
  
|
| Guest |
| Posted: Sun Feb 03, 2008 9:58 am |
|
|
|
Guest
|
----- "Tony Garnock-Jones" <tonyg@lshift.net> wrote:
> Hi all,
>
> I’ve just made our experimental STOMP adapter to RabbitMQ available.
>
> STOMP (http://stomp.codehaus.org/Home) is a very simple messaging wire
>
> protocol, with what appears to be fairly broad client support. I've
> only
> personally experimented with the Perl Net::Stomp client, but according
>
> to http://stomp.codehaus.org/Clients, there are a bunch of options
> available.
>
> Please try it out and let me know what you think! I've made a blog
> post
> summarising getting the thing running:
> http://www.lshift.net/blog/2008/02/02/how-to-run-rabbitmqs-experimental-stomp-adapter
>
> If you use mercurial, you can get a checkout of the adapter code with
>
> hg clone http://www.lshift.net/~tonyg/hg/hgwebdir.cgi/rabbitmq-stomp/
>
> I would have put the repository on dev.rabbitmq.com, but for some
> extremely unfortunate network setup issues we suffer from inside our
> firewall at present. Once we sort the problems out, all RabbitMQ
> mercurial repositories will be moving to dev.rabbitmq.com.
It would cool if the RabbitMQ Makefile used $(MAKE) instead of just executing "make". Some systems have multiple make versions, with different names. So "make" may not be GNU make. Using $(MAKE) solves this problem.
But so far Stomp support looks ok. Is the plan to include the protocol into the RabbitMQ tree later, or will be it always be an extra download?
> Regards,
> Tony
Tom
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post recived from mailinglist |
|
|
| Back to top |
|
| alexis |
| Posted: Sun Feb 03, 2008 11:11 am |
|
|
|
User
Joined: 06 Sep 2007
Posts: 80
Location: London
|
Tom
Thanks for your comments.
On Feb 3, 2008 9:53 AM, Tom Samplonius <tom@samplonius.org> wrote:
>
> But so far Stomp support looks ok. Is the plan to include the protocol into the RabbitMQ tree later, or will be it always be an extra download?
>
At this stage we are introducing experimental client packs and add-ons
on a strictly by-need basis, i.e. as the community produces them and
customers ask for them, and subject to resources. STOMP represents a
convenient bridge into existing environments, enabling folks to
benefit from RabbitMQ's stability. In the future we plan to be more
systematic about RabbitMQ client packs, and managing the tree to
include the clients that have emerged in this way.
Would you like to get involved?
alexis
--
Alexis Richardson
+44 20 7617 7339 (UK)
+44 77 9865 2911 (cell)
+1 650 206 2517 (US)
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Sun Feb 03, 2008 11:16 am |
|
|
|
Guest
|
On Sat, Feb 02, 2008 at 12:13:54AM +0000, Tony Garnock-Jones wrote:
> I’ve just made our experimental STOMP adapter to RabbitMQ available.
>
> STOMP (http://stomp.codehaus.org/Home) is a very simple messaging wire
> protocol, with what appears to be fairly broad client support. I've only
> personally experimented with the Perl Net::Stomp client, but according
> to http://stomp.codehaus.org/Clients, there are a bunch of options
> available.
Looks good.
I noticed in some other testing that Net::Stomp currently has a rather
large overhead as it does a getc for every single character in a
frame. Especially if you're consuming large messages (it was
noticeable around 8KB) then this has a huge overhead. It probably
would be quite easy to fix but I haven't looked into it yet.
David
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post recived from mailinglist |
|
|
| Back to top |
|
| tonyg |
| Posted: Sun Feb 03, 2008 2:57 pm |
|
|
|
User
Joined: 07 Nov 2006
Posts: 199
|
Hi Tom,
Thanks for the feedback.
Tom Samplonius wrote:
> It would cool if the RabbitMQ Makefile used $(MAKE) instead of just
> executing "make". Some systems have multiple make versions, with
> different names. So "make" may not be GNU make. Using $(MAKE)
> solves this problem.
Good suggestion. Done in CVS HEAD for the RabbitMQ broker, and in
mercurial default tip for the STOMP adapter. The next broker snapshot or
release will contain the change.
> But so far Stomp support looks ok. Is the plan to include the
> protocol into the RabbitMQ tree later, or will be it always be an
> extra download?
We want our codebase to be modular, but we don't want to force a bunch
of separate downloads.
So while the source trees will probably stay loosely coupled, we'll
probably provide some kind of preconfigured bundles of binary
functionality as single downloads in future.
I've also been thinking about a less ad-hoc way of extending the server
with plugins, but that's probably a wee way off.
Tony
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post recived from mailinglist |
|
|
| Back to top |
|
| tonyg |
| Posted: Sun Feb 03, 2008 3:07 pm |
|
|
|
User
Joined: 07 Nov 2006
Posts: 199
|
Hi David,
David Leadbeater wrote:
> I noticed in some other testing that Net::Stomp currently has a rather
> large overhead as it does a getc for every single character in a
> frame.
How were you testing it? Our Erlang STOMP serialiser always supplies a
content-length header, and from my reading of the Net::Stomp code, it
looks like it should use the content-length, when there is one, to do a
single block read.
Tony
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post recived from mailinglist |
|
|
| Back to top |
|
| tonyg |
| Posted: Sun Feb 03, 2008 3:17 pm |
|
|
|
User
Joined: 07 Nov 2006
Posts: 199
|
Hi again,
Tony Garnock-Jones wrote:
> How were you testing it? Our Erlang STOMP serialiser always supplies a
> content-length header, and from my reading of the Net::Stomp code, it
> looks like it should use the content-length, when there is one, to do a
> single block read.
I've just checked, by sending
$stomp->send({destination=>'foo',
bytes_message=>1,
body=>($ARGV[0] or "test\0message")});
that the receiver correctly handles embedded NULs - which means it's in
the branch that uses the content-length to do a block read. (Of course,
it's probably still not doing any buffering!)
I'd be interested to hear more about your testing, and how
RabbitMQ+STOMP performs for your use cases.
Regards,
Tony
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Mon Feb 04, 2008 4:23 pm |
|
|
|
Guest
|
Hi,
On Sun, Feb 03, 2008 at 03:17:15PM +0000, Tony Garnock-Jones wrote:
> >How were you testing it? Our Erlang STOMP serialiser always supplies a
> >content-length header, and from my reading of the Net::Stomp code, it
> >looks like it should use the content-length, when there is one, to do a
> >single block read.
Sorry, I meant I'd seen the issue against ActiveMQ, it seems to work
quite well with rabbitmq-stomp. I also just tested it out with
ActiveMQ CMS using STOMP and that seems to work OK.
David
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post recived from mailinglist |
|
|
| Back to top |
|
| tonyg |
| Posted: Mon Feb 04, 2008 11:56 pm |
|
|
|
User
Joined: 07 Nov 2006
Posts: 199
|
|
| Back to top |
|
| Guest |
| Posted: Mon Feb 18, 2008 9:50 pm |
|
|
|
Guest
|
Thank you for creating this adapter. I just tested it out with the
ActionScript (Flash/Flex) Stomp client and everything seemed to work quite
well. If anyone is interested, I wrote up a short post about it here:
http://flexonrails.net/?p=106.
Are you planning on adding any custom AMQP specific extensions to the
protocol like ActiveMQ does for JMS (see
http://activemq.apache.org/stomp.html)? It looks like there is already one
for specifying an exchange. Do you think you might add others?
Best,
Derek
Tony Garnock-Jones-2 wrote:
>
> Hi all,
>
> I’ve just made our experimental STOMP adapter to RabbitMQ available.
>
> STOMP (http://stomp.codehaus.org/Home) is a very simple messaging wire
> protocol, with what appears to be fairly broad client support. I've only
> personally experimented with the Perl Net::Stomp client, but according
> to http://stomp.codehaus.org/Clients, there are a bunch of options
> available.
>
> Please try it out and let me know what you think! I've made a blog post
> summarising getting the thing running:
> http://www.lshift.net/blog/2008/02/02/how-to-run-rabbitmqs-experimental-stomp-adapter
>
> If you use mercurial, you can get a checkout of the adapter code with
>
> hg clone http://www.lshift.net/~tonyg/hg/hgwebdir.cgi/rabbitmq-stomp/
>
> I would have put the repository on dev.rabbitmq.com, but for some
> extremely unfortunate network setup issues we suffer from inside our
> firewall at present. Once we sort the problems out, all RabbitMQ
> mercurial repositories will be moving to dev.rabbitmq.com.
>
> Regards,
> Tony
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss@lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
--
View this message in context: http://www.nabble.com/Experimental-STOMP-adapter-available-tp15237803p15549124.html
Sent from the RabbitMQ mailing list archive at Nabble.com.
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post recived from mailinglist |
|
|
| Back to top |
|
| tonyg |
| Posted: Thu Feb 28, 2008 8:08 am |
|
|
|
User
Joined: 07 Nov 2006
Posts: 199
|
Hi Derek,
Derek Wischusen wrote:
> Thank you for creating this adapter. I just tested it out with the
> ActionScript (Flash/Flex) Stomp client and everything seemed to work quite
> well. If anyone is interested, I wrote up a short post about it here:
> http://flexonrails.net/?p=106.
Awesome post!
> Are you planning on adding any custom AMQP specific extensions to the
> protocol like ActiveMQ does for JMS (see
> http://activemq.apache.org/stomp.html)? It looks like there is already one
> for specifying an exchange. Do you think you might add others?
Yes. I want to keep to the protocol definition as closely as possible,
but to provide extensions to allow people to use more of the
AMQP-specific features that are available. You're right about the
exchange extension. So far, refreshing my memory by looking at the code,
the extensions are:
- "virtual-host" and "realm" headers on CONNECT, for exploiting
RabbitMQ's implementation of AMQP's authorization features
- "exchange" on SEND - if omitted, the default ("") exchange is used
If you have anything in mind you'd like to see added, please let me
know. I need feedback to decide what direction to take the STOMP adapter in.
Regards,
Tony
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Sat Mar 01, 2008 9:55 pm |
|
|
|
Guest
|
Hey Tony,
The headers that you have listed probably cover all of the ones that I would want to see. |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
