Finally, we’ve named our new open source message queue framework “dropr”.
Why? When Boris was writing the client angel script he somehow named it “dropr”. As we neither got better suggestions nor had any other idea we just decided for this name. Actually the name is a little bit fun because all those stupidR startupRs. But it’s nice and somehow our framework drops message into queues :)
If you’re using google to search for it, it’s already the first result.
So have a look at https://www.dropr.org/. We’re just writing a little installation manual about setting up the pre-release of our framework. We’ll keep you up-to-date on this blog, so stay tuned.
December 10th, 2007 at 14:09
Some simple real-life example would be very useful ;)
December 11th, 2007 at 00:37
Hi Alexey,
I guess you mean a use-case. Think of a distributed architecture with servers all over the world. You can’t rely on synchronous webservice calls if you want to synchronize data of two servers. I’m sorry there is no more documentation at this stage of the project because it’s in an early state :)
June 19th, 2010 at 10:02
Think of a distributed architecture with servers all over the world. You can’t rely on synchronous webservice calls if you want to synchronize data of two servers.
July 29th, 2010 at 13:04
Hey this is really nice information. I was looking for something similar like this. Thanks for this useful information.
July 29th, 2010 at 13:05
hey buddy,this is one of the best posts that I’ve ever seen; you may include some more ideas in the same theme. I’m still waiting for some interesting thoughts from your side in your next post.
July 29th, 2010 at 13:05
Amazing..you really made my day & after reading this Surely..i ll twit this to my all friends to know more about this blog :)