Glenn & Brent,

> > Instead of putting httpinst into search.htm, make it a
> > search with it's own httpinst.xml similar to what I
> > did with configure.xml.

I thought about that, but it seems a bit unnecessary to clutter the
searches directory with system commands. I didn't think the overhead of
loading/parsing justified the modularity... Besides, what if someone
disabled httpinst!? That'd be a disaster (for my pride) ;)

> Yeah!  Good point.  There is a framework!

I sit corrected :)

I think I'll build a proper search function out of it, but leave it
within search.htm. I need to be able to munge parameters as well.

Cheers,
Kim



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
DQSD-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dqsd-devel

Reply via email to