Matt:
        Heya. Quick comment:

> > 1. To make UI design easier for everyone, it'd be *nice* if the user's
> >    intentions for the firewall were stored on the firewall in XML format.
> >    A firewall.conf, as it were.
>  
> I don't like this whole thread, but I'm a bit crotchety this morning.
> 
> I disagree with #1.  I don't want to have anything to do with XML, and
> if that's what's going to happen here, then it's not for me.  If someone
> wants to build up some cgi-scripts to do https configuration with the
> files that exist, I like  that idea, as it's possible with weblet or
> whatever and almost everyone has a browser.
> 
> I don't like the idea of a standard interface for all the flavors of Lrp.

        Okay. :) I think we're more in agreement than not.

        My intention was to speculate on the need for a bedrock piece 
for, specifically, a firewall UI. Having one would allow more focused work
by the "people who want to write UI's" and the "people that want to create
rulesets" and the "people who want to create new capabilities". Given a
basis, there could then be created multiple flavors of UI for a LEAF-based
firewall-router. Some would be GUI's, some lrcfg-like, some would look
suspiciously like ae. 
        So, IMO, it helps to create "focused diversity" if everyone who
did branch out didn't have to worry about the whole enchilada, ceiling to
floorboards. 
        Of course, it doesn't *have* to be XML. The alternative is a file
format that has agreed-upon "fixed" variable names of some sort (which 
I'm using now in my project).

cheers,
Scott


_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to