I'd prefer the synchronicity to be coupled with a reasonable timeout period and default exit status being fail on timeout. Would this mean tinkering with process priorities so that the calling shell/process is always serviced? Discussions on cdb envisages dealing with name pairs. Can we not extend this to a relational DB form? Each application will have to register an attribute to the object. E.g. eth0 is an object. Its attributes are address, mask.... If we install shorewall, the eth0 related parameters like masq, norfc1918 etc are boolean fields/attributes. If we do so, in CLI if we query the interface, we will not only get IP related info but also application related info. I'm in agreement with Ray that we must follow the Linksys/netgear route for GUI. Our strength will be availability of CLI also.
Warm regards Mohan > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Chad Carr > Sent: Tuesday, July 06, 2004 10:41 AM > To: [EMAIL PROTECTED]; > [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: [leaf-devel] Source: config > > > On Jul 5, 2004, at 9:58 PM, S Mohan wrote: > > > Chad and list, > > > The simple way is synchronous. Unfortunately synchronous is > generally slow, and, as you mentioned, a way for an > ill-behaved trigger script to make a mockery of the system. > > A decision that must be made, and soon. > ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
