public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
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@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] [PATCH] Allow vis daemon to serve mesh topology simultaneously in dot_draw and JSON format
Date: Thu, 21 May 2009 02:37:32 +0800	[thread overview]
Message-ID: <200905210237.32316.lindner_marek@yahoo.de> (raw)
In-Reply-To: <F6D9C212-B698-46E4-8AE3-FE76DAFD2C54@7degrees.co.za>

On Tuesday 19 May 2009 01:01:48 Antoine van Gelder wrote:
> After some great input from Marek I took a swing at rewriting my vis
> patch to allow serving of mesh topology simultaneously in dot_draw &
> json.
>
>
> * -j enables JSON server on port 2005
>
> * dot_draw continues to be served on port 2004 irrespective of whether
> -j is specified or not.

Nice patch - I just uploaded it.


> Some thoughts:
>
> * It is not the prettiest of patches but it works. Thinking about
> cleaner approaches makes my imagination drift in the direction of a
> simple plugin API such as OLSRd has, anyone else having any similar
> thoughts ? :)
>
> * I'm serving json on port 2005 - any alternative suggestions ?

The code itself is far from being pretty. As usual it started as a proof of 
concept grew into a temporary solution and is still around. It worked quite 
well so far but if you have ideas & energy to improve it, please go ahead. :-)

Regards,
Marek


      reply	other threads:[~2009-05-20 18:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 17:01 [B.A.T.M.A.N.] [PATCH] Allow vis daemon to serve mesh topology simultaneously in dot_draw and JSON format Antoine van Gelder
2009-05-20 18:37 ` Marek Lindner [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=200905210237.32316.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /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