<br><br><div class="gmail_quote">On Wed, Oct 29, 2008 at 5:27 AM, Alexis Richardson <span dir="ltr"><<a href="mailto:alexis.richardson@cohesiveft.com">alexis.richardson@cohesiveft.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Shashi<br>
<br>
<br>
On Wed, Oct 29, 2008 at 1:05 PM, shashi fernando <<a href="mailto:shash4evr@gmail.com">shash4evr@gmail.com</a>> wrote:<br>
> hi all,<br>
<br>
Hi :-)<br>
<div class="Ih2E3d"><br>
> im a final year student and looking for a project for my final year<br>
> (duration - 8 moths). Still im newbie to<br>
> RabbitMQ, but have experience on managing messaging protocols.<br>
> And i would like to carry out my project on management of distributed<br>
> systems while<br>
> making a contribution to open source world.<br>
<br>
</div>An excellent idea!<br>
<div class="Ih2E3d"><br>
<br>
> im glad if you guys can propose some ideas relating to my interested areas<br>
> and provide<br>
> useful information necessary.<br>
<br>
</div>One idea would be to look at what management tools are already<br>
provided by the underlying erlang/OTP platform, such as Appmon, and<br>
find a way to expose the most important ones to non-erlang users.<br>
There are lots and lots of ways that this could be done, but the<br>
easiest would be via completely language neutral means, e.g. HTTP,<br>
SNMP and of course AMQP.<br>
<br>
Another - complementary - idea is this: If you look at current<br>
research into systems management for the industry, people are saying<br>
that WS-Man is too complicated and that providing a RESTful interface<br>
would be better. Certainly RabbitMQ would be a good harness to show<br>
such an invention.<br>
<br>
Also, you could look at using queues to manage other things, by the<br>
command pattern.<br>
<br>
It all depends how much work you want to do yourself, and how much you<br>
want to make use of existing tools.<br>
<br>
Other folks on the list may have suggestions. Perhaps we can pool<br>
them and help you figure out which is best for your goals.<br>
<br>
alexis<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
><br>
> _______________________________________________<br>
> rabbitmq-discuss mailing list<br>
> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
> <a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
><br>
><br>
</blockquote></div><br>thank you guys for the ideas. since im newbie to this environment, i have very little knowledge regarding the erlang/OTP platform and WS-Man (but im going to lookin into them). Therefore can you please provide a more ellobaration on followings ,so than i can get the exact idea and work on it.<br>
<br>1. <i>find a way to expose the most important ones to non-erlang users.<br> </i>what the importance of such exposure<i> ?<br><br>2. WS-Man is too complicated and that providing a RESTful interface<br>
would be better. Certainly RabbitMQ would be a good harness to show<br>
such an invention.<br><br></i>thank you<br>shash<i><br></i>