|
|
| Author |
Message |
|
| 0x6e6562 |
 Posted: Mon Mar 03, 2008 3:54 pm |
 |
|
|
User
Joined: 12 Jul 2007
Posts: 250
|
Hi,
Sorry about the last email, my ASCII art wasn't very readable.
Here's an image.
HTH,
Ben
Post recived from mailinglist |
|
|
| Back to top |
 
|
| Guest |
| Posted: Wed Mar 05, 2008 9:19 am |
|
|
|
Guest
|
Hi Ben,
No problem - it was actually fairly readable although this is much
nicer 
Yep, I've thought about that and it does make sense. As I quite like
Hessian that might be the way to go. It wouldn't be to big a problem
to build into our existing commandline client and it could be part of
the generic-ish AMQP framework Alexis has been talking about which we
maght have the beginnig of.
Michael
On Mar 3, 2008, at 16:53 , Ben Hood wrote:
> Hi,
>
> Sorry about the last email, my ASCII art wasn't very readable.
>
> Here's an image.
>
> HTH,
>
> Ben
>
> <CLI Layering.png>
>
> On 3 Mar 2008, at 14:56, Ben Hood wrote:
>
>> Michael,
>>
>> On 3 Mar 2008, at 10:15, Michael Arnoldus wrote:
>>
>>> Ben,
>>>
>>> Currently we're using Python.
>>>
>>> Yes, I understand and appreciate your use of Hessian to go
>>> language neutrality. The only reason I have for changing this to
>>> something human readable is, that it makes it possible for me to
>>> use an already existing command-line client that is able to send
>>> and receive from AMQP - and I have this fantasy that most people
>>> would have such a command-line thingy - and it would be an
>>> extremely neat way to do almost all communication with the server.
>>
>> I take your point.
>>
>> Have you considered a layered approach to this problem?
>>
>> For example:
>>
>>
>> Client
>>
>> Rabbit Server
>>
>> ----------------------------
>> | Command Line |
>> ----------------------------
>> | CLI Parser |
>> ---------------------------- ----------------------------
>> | API Method | | API Invocation |
>> ---------------------------- ----------------------------
>> | Hessian Encoding | | Hessian Decoding |
>> ---------------------------- ----------------------------
>> | AMQP | ----------wire-------------->
>> | AMQP |
>> ---------------------------- ----------------------------
>>
>> That way you wouldn't need to write any server-side parsing and
>> response generation, and you can piggy back off an already existing
>> mechanism.
>>
>> All you would have to do is create the API definition in Python,
>> but this is just copying the Erlang module interface definition to
>> Python. All of the marshaling and unmarshaling is done for you.
>>
>> HTH,
>>
>> Ben
>
> _______________________________________________
> 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 |
|
|
|
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
