From:                   Martin Hejl <[EMAIL PROTECTED]>
To:                     [EMAIL PROTECTED]
Subject:                Re: [Leaf-devel] chains/rules schema - win client
Send reply to:          [EMAIL PROTECTED]
        <mailto:leaf-devel-
[EMAIL PROTECTED]?subject=subscribe>
        <mailto:leaf-devel-
[EMAIL PROTECTED]?subject=unsubscribe>
Date sent:              Fri, 02 Feb 2001 21:14:37 +0100

> "Scott C. Best" wrote:
> > Yikes, from schema to UI in 5 emails. :)
> LOL. You're absolutely right. But the way I read it, the reason for having a
> shema at all was to make a nice, user firendly frontend.

are you sure we read the same thread ?
As far as I (not natively english speaking) understood this emails 
they were discussing describing the firewall,router and its 
configuration in XML and just dreaming a little about  what you 
could do with that 



> > 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.
> > 
> > 2. Given this firewall.conf file, a middleware process/app/script would
> >    be needed to turn this data into the OS-specific firewall commands
> >    (e.g. ipchains, ipfwadm, netfilter, etc). This middleware piece could
> >    produce either a root-executable script, install the rules directly, 
> >    or even do both.
> I'd say, if we actually can come up with something like that (and make it
> generic enough to be extensible), that would be a great accomplishment. It
> would make life easier for everybody, and it would also make sure that
> helper apps written today don't have to be dumped when the next kernel
> release changes everything again.
> 
> > Is this a sensible design-model paradigm for LEAF?
> As far as I see it, absolutely. Not easily done (at least for me ;-)), but
> certainly worthwile.
> 
> Martin
Eric


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

Reply via email to