[OLSR-users] RE: Dot topology plugin

[Ignacio García Pérez]

> -----Original Message-----
> From: Andreas Tønnesen [mailto:(spam-protected)]
> Sent: Thursday, October 21, 2004 6:51 AM
> To: Ignacio García Pérez
> Cc: OLSR-users
> Subject: Re: Dot topology plugin
>
>
> Hi,
>
> I do not have too much time to work on plugins these days - and I have
> never really used the dot_draw plugin. So please submit patches - or
> even better, take over maintainance of the plugin ;)
> That beein said - if anybody is interested in taking over development of
> _any_ of the plugins then please let me know.

We are here considering programming a simple plugin that provides access to
OLSRD internal state. As mentioned in my previous message, it should allow
multiple clients.

This would be more flexible than providing a DOT description of the network.
If one wants a DOT description, a small program that connects, grabs the
OLSRD internal state, and generates the DOT would suffice. More modular.

Here are the alternatives. I would like to hear you opinion before starting
to code:

Threads:

1- Non-threaded plugin. Has the potential "send() block" problem I
described.

2- Threaded plugin. A bit more complex.

Notification/polling:

1- Notification: a client connects. Immediatelly, it gets the current OLSRD
internal state. Then, as long as the connection is open, it gets the new
state every time it changes.

2- Polling: a client connects, and sends a simple command to which the
plugin responds sending the OLSRD internal state.

Polling has the advantage that when implemented as a non-threaded plugin, it
is very unlikely to display the "send() block" problem, since the plugin
will send only upon request. If the clien vanishes from the network the TCP
buffers will not become full, unless the complete internal state is bigger
that the TCP buffers.

Nacho.
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.778 / Virus Database: 525 - Release Date: 10/15/2004