[Config4gnu-developer] Re: a new approach to "parsers"

[Justin Y. <ju...@sk...>]

On Thu, 2002-11-07 at 17:03, Jason Long wrote:
> How do you feel about making a change to the "parsers" & "unparsers" so that
> they always read their input on STDIN and output on STDOUT?


Sounds like a good idea to me, they do half of this already.  I will
make it happen when I redo all the parsers by this weekend.  If there
are any changes (i'm already changing parameter to property) that I
should make to the XML, let me know.


> Advantages:
>  - remote administration... the caller of the parser can read the file from
> a remote computer and pipes it to the parser. Parsers do not need to know
> how to read remote files
> 
> Disadvantages:
>  - parsers cannot work with multiple files
>    possible workaround: for configuration files with "includes", output it
> as an "external" node


You mean that the parser would include in the outputted XML a node which
the middle layer checks for and if present, calls the parser again for
each external file?  That would work, or maybe you meant something else?

>  - parsers can't run external commands to implement changes

Unless they output a shell script to accomplish the changes, and the
middle layer can detect this and run the script?


(this email address I'm sending from works, btw).


Justin


-- 
SkiingYAC.com
Custom Solutions
su...@sk...
http://www.SkiingYAC.com