The way we have handled this is to use the regular expressions capability
to replace the indexed file name with the frameset. That is, if
"mypage.html" is the page that sets up the frames and calls the other page
fragments, then name the page fragments uniquely and rename them in the
index using "ReplaceRules" in your configuration file.
mypage.html indexed under its own name
frag1.html indexed as "mypage.html"
frag2.html indexed as "mypage.html"
Thus all of the pieces point to the frameset.
On Mon, 28 Jun 1999, Dan Brickley wrote:
> On Mon, 28 Jun 1999, Matteo Barbieri wrote:
> > I successfully created my first index file in filesystem mode..
> > In http mode I found that the robot doesn't traverse the site
> > but stops on the first html
> > I don't get back any error so I am wondering if the spider is
> > frame aware.
> As an aside, it's difficult in the general case building a
> frameset-aware robot and search tool, since the composite-frameset
> doesn't have its own URL, so you'd need to auto-generate the appropriate
> frameset and populate it with the two or three appropriate URLs if you
> wanted to present users with the pages they'd found. (otherwise you can
> show them the page, but they'd lose all navigational context from the
> surrounding frame parts)
> Institute for Learning and Research Technology http://www.ilrt.bris.ac.uk/
> University of Bristol, Bristol BS8 1TN, UK. phone:+44(0)117-9287096
Received on Mon Jun 28 08:05:41 1999