On Fri, 16 Feb 2001, Lee Iverson wrote:
> Don't ignore it. Put simply, Paths are client-side, transient objects --
> they are context holders. Path Descriptions would, however, be stored in
> the Repository.
This is one point I had a lot of trouble with. Path descriptions are
stored in the repository. The client generates a directed graph of nodes
using Path objects based on information from the repository. Conceivably,
for a single document, there could be a different path tree for every user
who accesses the document.
My question is, why do you need separate Path objects on the client side?
What's wrong with just having a list of child nodes as a property of the
client-side Node object? It seemed to me that the reason for Path objects
would be to have multiple trees without having to touch any of the nodes.
That, to me, seems to be a repository issue, not a client-side issue, as
the client is only going to see one possible tree based on its
-- +=== Eugene Eric Kim ===== firstname.lastname@example.org ===== http://www.eekim.com/ ===+ | "Writer's block is a fancy term made up by whiners so they | +===== can have an excuse to drink alcohol." --Steve Martin ===========+
This archive was generated by hypermail 2.0.0 : Tue Aug 21 2001 - 17:58:02 PDT