From: Kevin Steen <batman@kevinsteen.net>
To: "b.a.t.m.a.n@lists.open-mesh.org" <b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Format stable?
Date: Sat, 19 Mar 2011 23:53:43 +0000 [thread overview]
Message-ID: <4D854207.3090508@kevinsteen.net> (raw)
In-Reply-To: <201103192054.24811.lindner_marek@yahoo.de>
On 19/03/11 19:54, Marek Lindner wrote:
>> On a related note, is the on-air format for batman_adv reasonably stable
>> at the moment? If thousands of FreedomBoxen[1] were to start using it,
>> what's the likelihood they would all have to upgrade to a new wire
>> format in the near future?
>
> you might want to define "reasonably stable" for your use case to allow us to
> give you an equally reasonable estimate. However, mesh technology is pretty
> young and many ideas are flowing around to further improve it. I am sure the
> formats will change some day.
:-) Good answer to a poor question!
I think what I should have asked is whether there are any format changes
already planned and defined, just waiting for the code to be signed-off?
I know there will always be unexpected changes to address problems which
get discovered, but as long as there aren't changes already in the
development pipeline, I would call that "reasonably stable".
Since BattleMesh is currently running, and will probably generate many
new ideas, I think I should withdraw my question and ask again in a few
weeks!
-Kevin
prev parent reply other threads:[~2011-03-19 23:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 17:12 [B.A.T.M.A.N.] Software editing of /etc/network/interfaces ? Kevin Steen
2011-03-19 19:54 ` Marek Lindner
2011-03-19 23:53 ` Kevin Steen [this message]
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=4D854207.3090508@kevinsteen.net \
--to=batman@kevinsteen.net \
--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