Lynn At 04:50 01.07.2002, you wrote:
>James Sturdevant posted POST support in patch form to the list a while >back. I think this will work fine. I would be very interested in that patch. I changed sh-httpd to support a GET with multiple parameters to at least be able to use forms in a still very primitive state, but of course a fully fledged POST would be superior. > > Performance: The sh-httpd server is kind of slow when serving up CGI > > pages. This is due to the way the shell-script handles spawning the > > child CGI process, and checking to see if it's finished. I think > > this can be re-architected to perform much better...when I was > > working on sh-httpd, I didn't know I could open multiple file-handles > > in shell-script, which makes the above problem easier. > >I don't think much CGI would be required with the use of forms, ash >scripts, and limiting access to localhost. Agreed, performance is not that big an issue with configuration. >I agree 100% with that statement. >I am using forms (of course), which POST on individual lines. I think >sed and stock ash are fine w/o needing mawk. The forms would use >stock variables (ie... eth0_IP_ADDR) when the "option" sets a single >variable and a new variable to set several "stock" variables when >applicable (ethernet-dhcp, ppp-dhcp, etc...). The added scripting needed >to interpret the added variables would be put in network.conf. As far >as changes to the network.conf "standard", I propose modularizing >certain sections of declared variables into their own form/conf file, >then "sourcing" these new conf files into the "script-only" >network.conf file. Example of the break-up of network.conf would be >something along the lines of "base-config, advanced-net, qos, and dmz." >This will minimize the amount of needed CGI code run. This would also >allow for a CLI-config set of scripts so that you can edit all >configuration on the LEAF machine itself with the same ash/cgi scripts >that the web-based admin uses. Thoughts??? I would not necessarily break up network.conf. Neither is it necessary to have the functions implemented there, at least not for the development cycle. I would make it a separate package unless it fits nicely on a floppy. How far advanced are you? I would hate to replicate your work. regards Erich THINK P�ntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
