> However, this goes against the Plucker format, which dicates a
> hierarchical, rather than a linear, structure. I.e. there is just
> one"home" record and through that you branch out to the other pages.
Not at all. This is why the home.html construct works (and it's the
foundation that Plucker was originally based upon). You have a home.html,
which resembles the following (excuse the horrible ascii art):
[home.html]
/ | \
/ | \
p1 p2 p3
/|\ /|\ /|\
/ | \ [ repeat ]
c1 c2 c3
..and so on. You now have three "root nodes" from which to fetch
child nodes from. From here, you tree in a depth-first parsing run, after
the breadth-first run sweeps across p1, p2, and p3 (parent 1, 2, and 3).
From here, you view home.html in Plucker, and have 3 links available
to you for viewing. Call them "bookmarks" if you wish. You can then drill
"down" through those, to get to the content you want.
I've mentioned before, and maybe it merits mentioning again. There
is no "up" or "down" on the internet. Links are exactly (and never more)
than a depth of 1 from every other link on the entire internet. Applying a
"directory" meme to the internet doesn't compute. That being said, you can
have multiple starting points, from which to spider (of course, you have to
be careful to track and eliminate duplicates during the run), but there is
no need to replicate what iSiloX has to achieve this, it already exists.
d.
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
