"tunneling" AMQP messages via another protocol (e.g. FTP)

[Fraser Adams <fr...@blueyonder.co.uk>]

Hi all,
I've got a scenario where I have a consumer who for various reasons 
can't connect directly to my AMQP infrastructure.

I want to be able to share messages with them in a fairly lightweight 
and hopefully standards based manner. Some of the metadata contained in 
the AMQP headers we've populated is significant so needs to be preserved 
over the communication channel and the message body is essentially 
viewed as an opaque octet array.

These consumers primarily expect things to be delivered to them via FTP.

My initial thought is to use MIME. So I'd create a MIME message, write 
my message body to the MIME body part and map the AMQP headers to MIME 
"x-" headers.

This approach feels simple and workable, but I wanted to sound out the 
Qpid community to see if anyone else has had this scenario and what 
approaches others have used.

I don't suppose that there are standard "patterns" for this sort of 
thing are there?

Although the MIME approach is simple and essentially standards based I'd 
rather not go reinventing any wheels.

Cheers,
Frase

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org