At 01:39 PM 6/18/01 -0500, Gilles Detillieux wrote:
>According to Dan Langille:
> > > The work in progress is available at:
> > > http://diary.unixathome.org/htdig/results.php
> >
> > I've made some progress. See the code at
> > http://diary.unixathome.org/htdig/results.php.txt
> >
> > The next step is to take the incoming parameters from
> > $QUERY_STRING, split them, and feed them into the call to htdig.sh
> > (see #2 listed below).
> >
> > > If you search on 'langille', you'll get two pages of results. If you
> examine
> > > the URLS provided for the (2) link, you'll find:
> > >
> > > http://diary.unixathome.org/htdig/?config=htdig;format=htdig;words=langil
> > > le;page=2
> > >
> > > As I see it, there are two problems to solve:
> > >
> > > 1 - get the correct URL in there. It should be
> > > http://diary.unixathome.org/htdig/results.php
> >
> > This has been done.
>
>I assume you discovered the "script_name" attribute. It was added
>specifically for supporting PHP wrappers around htsearch.
I suppose there's that too :)
> > > 2 - parse the arguments
> > > "?config=htdig;format=htdig;words=langille;page=2" into something php
> > > can use.
> >
> > Anyone want to try this? I'm off to bed.
>
>Hope you had a good sleep. I'm not sure, but I though someone on the list
>once mentioned that the latest version of PHP does support parsing query
>strings that use a semicolon as separator. (Maybe I'm confusing this with
In theory, it does. However, I personally find it a bass-ackwards
implementation. It probablt has something to do with PHP using semi-colons
as line endings. Until PHP handles semi-colons properly, I'll still opt for
the string replace method.
-C
--
Curtis Ireland - [EMAIL PROTECTED]
Solidum Systems - http://www.solidum.com
(T) (613)724-6004 x284 - (F) (613)724-6008
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
