Re: Wrapper configuration
"Jon Sumpster" <[email protected]>
| Newsgroups | gmane.comp.web.htdig.general |
|---|---|
| Message-ID | <[email protected]> |
Thanks Jim, that is a great help. Best Regards Jon >From: Jim <[email protected]> >To: Jon Sumpster <[email protected]> >CC: [email protected] >Subject: Re: [htdig] Wrapper configuration >Date: Wed, 23 Mar 2005 23:04:23 -0700 (MST) > >On Mon, 21 Mar 2005, Jon Sumpster wrote: > >>I wonder if you might have any pointers for my situation; in our >>application, the 'wrapper' is an HTML page that's content is dynamically >>rendered when it's URL is called, and in which the appropriate content >>(such as links, images, styling etc.. which can change over time) is >>placed. > >I think that there are at least a couple ways to achieve the results that >you are looking for. More below. > >>the appropriate position); the only apparent alternative is to create a >>static wrapper page which resides in the common directory, but then that >>needs updating as the design of the site changes, something that I was >>hoping to avoid as it defeats the 'change once, apply everywhere' >>principle. > >Depending on the frequency with which updates occur, you might consider >setting up a cron job, or similar, that periodically retrieves the current >templates from the remote machine using something like curl, wget, scp, >etc. It is a bit of a kludge, but it might do the trick for infrequent >updates. > >>Is there perhaps a way that we can call the htsearch program to return a >>stream rather than an HTML page, which can then be manipulated and placed >>in the required position? > >Yes, I think that you could achieve this type of functionality with a >wrapper script. You would need something that accepted a query, called >htsearch behind the scenes, and then built the result page based on what >was returned by htsearch. If you strip the local templates of HTML and >leave only the variables you are interested in, you should be able to get >back something vaguely resembling a stream. > >If this sounds like it might be an option, take a look at the following. > > http://www.devshed.com/c/a/PHP/Search-This/ > >While it is not directly applicable, it should provide some insight into >how you might go about wrapping your call to htsearch. It also provides >examples of modified templates that support some other entity building the >final result page. > >Jim ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ ht://Dig general mailing list: <[email protected]> ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-general