[rabbitmq-discuss] Fwd: python stomp examples

Wed Sep 10 11:24:47 BST 2008

FYI, this is how Jason replied to me about stompy + Rabbit.

---------- Forwarded message ----------
From: Jason Briggs <jasonrbriggs at gmail.com>
Date: Mon, Sep 8, 2008 at 10:12 PM
Subject: Re: [rabbitmq-discuss] python stomp examples
To: 0x6e6562 at gmail.com

Looks like he's resolved his problem by using something else.  My
stomp code pretty much hasn't been touched in months (I'm not
supporting it any more), so I'm not surprised it doesn't work.  As a
matter of interest, it still works correctly against ActiveMQ (I just
checked), but when I tried against Rabbit I got a similar problem.
Weird... but I've got no time to investigate why.

On 8 Sep 2008, at 16:55, Jason Briggs wrote:

>
>
> -----Original Message-----
> From: Ben Hood [mailto:0x6e6562 at gmail.com]
> Sent: 08 September 2008 16:54
> To: Novak Joe
> Cc: rabbitmq-discuss at lists.rabbitmq.com; Jason Briggs
> Subject: Re: [rabbitmq-discuss] python stomp examples
>
> Joe,
>
> On Mon, Sep 8, 2008 at 4:26 PM, Novak Joe <joes.mailing.lists at gmail.com>
> wrote:
>
>>> BTW, is your goal to speak to Rabbit from Python fullstop, or do you
>>> specifically need to use STOMP?
>>
>> I specifically need to use STOMP, and I want to integrate this with
>> Orbited ( www.orbited.org ), and an existing pylons application.
>
> Sure. BTW, have you read this article:
> http://orbited.org/blog/2008/09/integrating-orbited-with-web-app-framewo
> rks/
>
>> The stomp.py test program I'm using, which comes directly from the
>> site mentioned in my original post, is still giving the following
>> error:
>> ERROR
>> message: Bad CONNECT
>> content-length: 36
>>
>> Missing login or passcode header(s)
>>
>> despite my most certainly sending the headers.  But I suspect there is
>
>> some descrepancy between this and the ruby examples that ship with the
>
>> stomp adapter source, so maybe a bit of digging around will be
>> sufficient for me to solve this!
>
> Maybe Jason (cc'ed) can help debug this?
>
> Ben
>
> *****************************************************
> This email is issued by a VocaLink group company. It is confidential and intended for the exclusive use of the addressee only. You should not disclose its contents to any other person. If you are not the addressee (or responsible for delivery of the message to the addressee), please notify the originator immediately by return message and destroy the original message. The contents of this email will have no contractual effect unless it is otherwise agreed between a specific VocaLink group company and the recipient.
>
> The VocaLink group companies include, among others: VocaLink Limited (Company No 06119048, VAT No. 907 9619 87) which is registered in England and Wales at registered office Drake House, Homestead Road, Rickmansworth, WD3 1FX. United Kingdom, Voca Limited (Company no 1023742, VAT No. 907 9619 87) which is registered in England and Wales at registered office Drake House, Three Rivers Court, Homestead Road, Rickmansworth, Hertfordshire. WD3 1FX. United Kingdom, LINK Interchange Network Limited (Company No 3565766, VAT No. 907 9619 87) which is registered in England and Wales at registered office Arundel House, 1 Liverpool Gardens, Worthing, West Sussex, BN11 1SL and VocaLink Holdings Limited (Company No 06119036, VAT No. 907 9619 87) which is registered in England and Wales at registered office Drake House, Homestead Road, Rickmansworth, WD3 1FX. United Kingdom.
>
> The views and opinions expressed in this email may not reflect those of any member of the VocaLink group. This message and any attachments have been scanned for viruses prior to leaving the VocaLink group network; however, VocaLink does not guarantee the security of this message and will not be responsible for any damages arising as a result of any virus being passed on or arising from any alteration of this message by a third party. The VocaLink group may monitor emails sent to and from the VocaLink group network.
>
> This message has been checked for all email viruses by MessageLabs.
> *************************************************************