Re: [serval-project-dev] Implementing a different routing protocol
On Sat, Dec 15, 2012 at 12:47 AM, Fraser Cadger <cadge01@googlemail.com> wrote:
I had actually been meaning to send another message about Rhizome for some time. I did some research into the code and I also came across a blog post by yourself discussing your tests with Rhizome implemented over MDP; http://servalpaul.blogspot.co.uk/2012/12/rhizome-over-mdp.html . I find the concept of the Rhizome journalling quite interesting, and I think it would definitely be relevant for the sharing of on-demand (recorded files), however I am not sure if it would work for the interactive video calling/VoIP traffic, but I must admit I have not looked at Rhizome in much detail so I could be wrong. Actually one question I have, leading on from your blog post; is Rhizome intended to be implemented over MDP? If so, aside from the journal concept of a file being a version which can be updated, and the use of store and forward, is there much of a difference between Rhizome routing and MDP routing?
Rhizome doesn't route. It just floods, one hop at a time. Though now that we have a rhizome transport built on MDP it would be possible to transfer content directly over a number of hops. Just because we have a novel tool doesn't make it a good fit for every problem. Just because you have a good hammer, doesn't make every problem a nail. -- You received this message because you are subscribed to the Google Groups "Serval Project Developers" group. To post to this group, send email to serval-project-developers@googlegroups.com. To unsubscribe from this group, send email to serval-project-developers+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/serval-project-developers?hl=en. ----- End forwarded message ----- -- Eugen* Leitl <a href="http://leitl.org">leitl</a> http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE
participants (1)
-
Jeremy Lakeman