Re: Howto read line from a stream

[Georg Bauhaus <rm.dash-bauhaus@futureapps.de>]

Dmitry A. Kazakov schrieb:

> Do you plan an admin position for your ball-point pen? You must be a very
> wealthy man...

Reminds me that I need to get one or two ballpen refills.

> The point is, either the configuration is trivial and you don't need any,
> or else it is non-trivial and then a representation of it as a tree does
> not work.

What would be the reason that trees don't work?
I notice that alternative formats have tree structure, such as

Name.Space.This = 123
Name.Space.That = foo
Another.Thing = bar

Dot, almighty...
(Java properties files).


> XML is rooted in dark ages of computing,

The dark ages of configuration are not over, and they will
not be over as long as we are here;  remember the
protocols being written in quality C?  ;-)

> from the times when people didn't
> really understand that there is no data. Because data without behavior is
> noise.

Data and behavior can have a *separate* representation
when moving between parts of a technical process.


> It
> does not add any value.

Config data does not need to *add* value.
Just *provide* values.  Valid values.  XML validation
is a start, and can be performed anywhere.
Here in the chain XML can add value to some technical
production process.


> My middleware binds publishers and subscribers without XML.

Since you are the one who has written the
middleware (a one producer connected system?
long term maintenance contracts? cooperative
atmosphere?),
I suppose it is unlikely processing some cleverly
made outside octet format such as videotext.


> If input is connected, it cannot be outside my responsibility.

Producing data can be an outside your responsibility.
I'd expect input validation to be more likely successful
when data has been preprocessed.  This is somewhat
like a journalist would be responsible, in part, for
what he writes before the editor does his work.