[7632] in www-talk@info.cern.ch
Re: Client-side highlighting; tag proposal
daemon@ATHENA.MIT.EDU (Gavin Nicol)
Sat Mar 11 08:42:11 1995
Date: Sat, 11 Mar 1995 08:30:01 +0500
Errors-To: procmaster@www19.w3.org
Reply-To: gtn@ebt.com
From: Gavin Nicol <gtn@ebt.com>
To: Multiple recipients of list <www-talk@www10.w3.org>
>That is, your search engine asks for content with word X returns the url of
>html page A which contains page A with all the X's surrounded by the highlight
>tag. Then, another search request for content with word Y happens to return
>page A (coincidentally contains Y too), but here with all the Y's tagged.
>Same URL, different associated HTML. This creates problems for profiling,
>expiration, other visited-page management facilities.
DynaWeb suffers from this, and in addition, it has named stylesheets
and whatnot, so there can be quite a large number of HTML "pages"
associated with any addressed element in the SGML document being
accessed. In addition, the auto-generated TOC's might be interesting
for Spiders...
>Of course, the construction of the URL being returned all depends on
>how you write your gateway...
True enough. DynaWeb has 3 subdocument addressing modes (read: URL
formats), and uses the ?foo=bar construct extensively...
I should note that DynaWeb is a native HTTP server.
