>> This means moving from a passive symlink to an ACTIVE
>> symlink. (Or have two different types of symlinks.)
Passive
>> in the traditional sense that it just points to something
>> somewhere else, and active being that the symlink has
some
>> intelligence/features build into it.
>Can you elaborate on this? I think the passive symlink is
what we've
>been discussing so far (with or without attached
properties), but I
>don't know what you would have in mind for active symlinks.
A UNIX symlink is passive or "dumb." It only refers people
to some file or directory somewhere else.
Now think about an active or "intelligent" symlink that I
could program to expire after a week? The original file is
untouched, but the user only sees that the file has
dissapeared or some other aspect of it (like its
attributes).
OK. Let's think of it a little different...
Perhaps, instead of thinking of it strictly as a "symlink",
think of it as a type of article that can pull the data
(properties) that I select from another article. In the
primary case the "abstract" and "content" data.
Componentizing the components, as it were.
A special type of article (say a symArticle) that is pulling
the data from another article, but this SymArticle has its
own properties that I can set individually. I could have one
master article, with 50 symArticles, each with their own
properties, and I can update the abstract and content in all
50 symArticles from one place.
Todd Daniel Woodward
Technical Consultant
RadioDigest.com Inc.
http://radiodigest.com
512/583-5448 Office
512/415-6840 Cell
"Radio you can READ!"
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
