Nabble - codehaus - Stomp

Doreen Kehoe/CA/GM/GMC is out of the office.

2009-12-07T01:00:25Z

I will be out of the office starting 11/27/2009 and will not return until
12/31/2009.

My last day of employment with GM is Friday, November 27, 2009 for all work
related matters please send your requests to liz.daly@... or call
905-644-4834.

Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message.

Confidentiality Note: This message is intended only for the person or entity to which it is addressed. It may contain confidential and/or privileged material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this message in error, please contact the sender and delete it from your computer.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: stomp - dev

Re: New Python broker: CoilMQ

2009-12-06T23:24:03Z

Nice work Hans!
On 7 Dec 2009, at 03:25, hozn wrote:

>
> Hi -
>
> I'm not 100% sure this is the right place to mention this, but I
> figure I'll
> only get yelled at a little if I'm wrong :)
>
> I've started a new, pure-python STOMP message broker project, and just
> pushed out the first (alpha-quality) release:
> http://code.google.com/p/coilmq/
>
> As mentioned (on that page), this project draws inspiration from the
> design
> of the Ruby StompServer project, which I think is a wonderfully
> clean &
> simple implementation. (I communicated with Patrick Hurley about
> this to
> make sure he was aware of the effort and to chat about licensing.)
> This has
> been largely a hobby/learning exercise for myself; while I've had
> great
> success with running ActiveMQ for modest STOMP needs in my day job, it
> bothered me that I couldn't find a working Python stomp broker out
> there. I
> felt this was a gap worth filling.
>
> If possible, I'd like to ask that this be mentioned on the main
> "Brokers"
> page. I have added mention of it to the bottom of the Python wiki
> page:
>
> http://docs.codehaus.org/display/STOMP/Python
>
> Thanks,
> Hans
> --
> View this message in context: http://old.nabble.com/New-Python-broker%3A-CoilMQ-tp26670270p26670270.html
> Sent from the stomp - dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

Rob Davies
http://twitter.com/rajdavies
I work here: http://fusesource.com
My Blog: http://rajdavies.blogspot.com/
I'm writing this: http://www.manning.com/snyder/

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: stomp - dev

Re: New Python broker: CoilMQ

2009-12-06T20:17:34Z

This is great!

On Sun, Dec 6, 2009 at 8:25 PM, hozn <hans@...> wrote:

>
> Hi -
>
> I'm not 100% sure this is the right place to mention this, but I figure I'll
> only get yelled at a little if I'm wrong :)
>
> I've started a new, pure-python STOMP message broker project, and just
> pushed out the first (alpha-quality) release:
> http://code.google.com/p/coilmq/
>
> As mentioned (on that page), this project draws inspiration from the design
> of the Ruby StompServer project, which I think is a wonderfully clean &
> simple implementation. (I communicated with Patrick Hurley about this to
> make sure he was aware of the effort and to chat about licensing.) This has
> been largely a hobby/learning exercise for myself; while I've had great
> success with running ActiveMQ for modest STOMP needs in my day job, it
> bothered me that I couldn't find a working Python stomp broker out there. I
> felt this was a gap worth filling.
>
> If possible, I'd like to ask that this be mentioned on the main "Brokers"
> page. I have added mention of it to the bottom of the Python wiki page:
>
> http://docs.codehaus.org/display/STOMP/Python
>
> Thanks,
> Hans
> --
> View this message in context: http://old.nabble.com/New-Python-broker%3A-CoilMQ-tp26670270p26670270.html
> Sent from the stomp - dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: stomp - dev

New Python broker: CoilMQ

2009-12-06T19:25:06Z

Hi -

I'm not 100% sure this is the right place to mention this, but I figure I'll only get yelled at a little if I'm wrong :)

I've started a new, pure-python STOMP message broker project, and just pushed out the first (alpha-quality) release: http://code.google.com/p/coilmq/

As mentioned (on that page), this project draws inspiration from the design of the Ruby StompServer project, which I think is a wonderfully clean & simple implementation. (I communicated with Patrick Hurley about this to make sure he was aware of the effort and to chat about licensing.) This has been largely a hobby/learning exercise for myself; while I've had great success with running ActiveMQ for modest STOMP needs in my day job, it bothered me that I couldn't find a working Python stomp broker out there. I felt this was a gap worth filling.

If possible, I'd like to ask that this be mentioned on the main "Brokers" page. I have added mention of it to the bottom of the Python wiki page:

http://docs.codehaus.org/display/STOMP/Python

Thanks,
Hans

From forum: stomp - dev

Fwd: Error on http://stomp.codehaus.org/Home

2009-11-16T15:27:12Z

FYI

---------- Forwarded message ----------
From: Andrew Kevin Bailey <abailey@...>
Date: Tue, Nov 17, 2009 at 9:21 AM
Subject: Error on http://stomp.codehaus.org/Home
To: bob@..., bwalding@..., support@...

Dear Mr. McWhirter and Mr. Walding:

There is a fairly substantial mistake on the web page
http://stomp.codehaus.org/Home. Under the section Stomp Brokers there
is a sentence regarding StompConnect. This sentence states, “The only
significant message broker which doesn't implement JMS is TibCo's RV
which is now legacy and the long term replacement is TibCo EMS which
does support JMS.” Both assertion of this sentence are incorrect.

For one, TIBCO Rendezvous is not a “message broker”. There is no
central hub or server which routes the messages. It is a true
messaging bus which uses broadcast, multicast, or a specialized
hardware accelerator appliance to facilitate communication between
clients. It is not in the same messaging classification as IBM MQ,
MSMQ, or JMS, which all rely on a software based central routing
server.

Second, TIBCO Enterprise Messaging Service is not indented to replace
TIBCO Rendezvous. TIBCO Enterprise Messaging Service is a 100% JMS
compliant messaging server and is intended for general purpose
messaging. Whereas TIBCO Rendezvous is designed for high rate and
ultra low latency messaging and does not support all of the features
of TIBCO EMS messaging.

It would be appreciated if you could correct the statement to say
something like: “The only significant message product which doesn’t
implement a JMS API is TIBCO Rendezvous. However, TIBCO Enterprise
Messaging Service does support JMS and is better for general purpose
messaging.”

Kind Regards,

A. Kevin Bailey

Enterprise Architect

TIBCO Software Inc.

--
Ben Walding :: ben@...
Web: http://openxource.com/

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: stomp - dev

PHP Stomp client moved

2009-11-05T04:40:37Z

Hi,

just to let you all know (with a small delay) that PHP Stomp Client, previously hosted on Google code and documented here has been moved to FUSEForge (http://stomp.fusesource.org/documentation/php/index.html). Incidentally, I released the 1.0.0 version with some bug fixes, so fi you're interested give it a spin.

I updated php page to reflect this move http://stomp.codehaus.org/php and also added a Zend framework's Zend_Queue to the list of available clients

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

Dejan Bosanac

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

Nabble - codehaus - Stomp

Doreen Kehoe/CA/GM/GMC is out of the office.

Re: New Python broker: CoilMQ

Re: New Python broker: CoilMQ

New Python broker: CoilMQ

Fwd: Error on http://stomp.codehaus.org/Home

PHP Stomp client moved

PHP Stomp client moved

Re: How to bind StompConnect on all network interfaces

How to bind StompConnect on all network interfaces

Ruby Stomp with timeouts

Re: JBOSS messaging and stompConnect

Re: StompConnect can not deliver messages to Jboss if name of destination contains / (slash)

StompConnect can not deliver messages to Jboss if name of destination contains / (slash)

Re: JBOSS messaging and stompConnect

does stompconnect work with OpenMQ in Glassfish?

[jira] Created: (STOMP-18) Itc Spanking Personals

[jira] Created: (STOMP-17) Jeremy Sumpter Shirtless

[jira] Created: (STOMP-16) Jack Owen Fanfiction Torchwood

[jira] Created: (STOMP-15) Etvx Model

[jira] Created: (STOMP-14) Valerie Plame Nude

[jira] Commented: (STOMP-13) Mylexus 7 34

[jira] Deleted: (STOMP-13) Mylexus 7 34

[jira] Created: (STOMP-13) Mylexus 7 34

Re: Stomp Future

Stomp Future

Re: Stomp Problem with receiving topic

Re: Stomp Problem with receiving topic

Re: Stomp Problem with receiving topic

Re: Stomp Problem with receiving topic

Stomp Problem with receiving topic

Re: Socket error disconnect resource leak

Re: JBOSS messaging and stompConnect

JBOSS messaging and stompConnect

Stomp C code with SSL?

Re: memory allocation bug in C client library