> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Kim Gr�sman > Sent: Thursday, June 26, 2003 7:52 AM > To: [EMAIL PROTECTED] > Subject: RE: [DQSD-Devel] httpinst intrinsic command > > > Thanks for the feedback! > > Comments inline: > > Monty said: > > localsearches are for the users private xml files, as opposed to the > > distrubuted ones - whether they are fetched via the web or > > installed with the package.... > > I guess I saw it as /localsearches are for the searches the user wants > to preserve, while /searches is free for the installer to modify at > will. Explicitly installing a search indicates to me that you'd like to > preserve it. IMHO, of course. >
Exactly.. I think we are saying the same thing.. You cant put the newly downloaded searches in the localsearches directory because you might over-write one of the users personal or modified searches. > MLL said: > > For me, the best would be to add another directory ; > > something like /websearches or /dlsearches > > I guess we could do that, but I don't see any benefits... They are just > searches, aren't they? Why separate them? It would mean having to read > searches from there as well on startup, which may be a bit complicated. > Why isn't the regular searches directory the right place to put these? Am I missing something? Unless I dont understand, (which is quite possible), the only logical place to put the searches - regardless of where they were collected - is the regular searches directory... Monty ------------------------------------------------------- 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
