From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] B.A.T.M.A.N Suitability for MAGIC 2010
Date: Tue, 16 Mar 2010 12:38:09 +0800 [thread overview]
Message-ID: <201003161238.09704.lindner_marek@yahoo.de> (raw)
In-Reply-To: <67B8674E-E8BB-4EE6-B368-F28AA0C957AB@me.com>
Hi,
> With regards to the type of middleware that I am searching for. Well,
> pub/sub with reliable and unreliable QoS is what we will most likely
> be using. I don't want to rush into a solution that buries the network
> in traffic from inter-broker communication, nor do I want to choose a
> middleware that fails in ad-hoc type networks. In any case, the
> middleware must hold up against repeated network partitioning and
> merging.
I'm not aware of any software which was specifically designed to operate over a
mesh network (apart from mesh routing daemons of course). Everybody simply
uses normal network operations and lets the lower layers handle the magic.
Therefore they are all equally "bad" (unless someone can name a positive
example) :-).
If you are interested in QoS you should make use of the wifi's QoS as Linus
suggested.
> If we do use B.A.T.M.A.N we will likely be using the layer-2 flavor
> running on a router with openWRT. So drivers will not be an issue,
> just router selection.
Ok.
Cheers,
Marek
next prev parent reply other threads:[~2010-03-16 4:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 14:12 [B.A.T.M.A.N.] B.A.T.M.A.N Suitability for MAGIC 2010 Michael Fazio
2010-03-14 20:41 ` Linus Lüssing
2010-03-15 11:23 ` Michael Fazio
2010-03-15 11:44 ` Marek Lindner
2010-03-15 12:35 ` Michael Fazio
2010-03-16 4:38 ` Marek Lindner [this message]
2010-03-14 23:32 ` L. Aaron Kaplan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201003161238.09704.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox