On Sam, 2008-01-05 at 00:26 +0100, Aaron Kaplan wrote:
> On Jan 5, 2008, at 12:20 AM, Clemens Hopfer wrote:
[...]
> > I thought about a scenario where you could want to leave the  
> > connection open,
> > that would be good for an application which continously needs the  
> > topology
> > (to show its changes for example).

And especially if you want to get really all changes (given hardware
that can cope wit it). Automatic close adds race conditions to that and
there is no way to turn it off.
If a "reverse-engineered" list of changes on one node is of any real
value, is another question.

> > It might be interesting having an option in the config file to turn  
> > it off.
> >
> > But afaik there can only be one connection at a time.
> 
> that is true, and a major critique for the dot_draw plugin until now.

The trivial and simple solution is: the only user of that plugin is
itself a multiplexer, either (again) via TCP or into files with
different names or shared memory/semaphor or whatever method you
need/want/like.

> Any general high quality re-write of dot_draw would be welcome and  
> accepted with open arms :)

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services




