Hi all, just a quick note from Spain,
I�ve been doing the prep work on DAV support, and I�ve run
into some challenges. We�ll discuss them in full when I�m
back, but this is just to get your brains in gear on the subject.
On the high level, there�s the issue that DAV is focussed mainly on the
filesystem-like implentation. For example, it expects objtcts that
will be rendered as pages to exists at all times, which is not
rthe case with Midgard: pages exists when they�re called up by a viewer.
This is a challengge, but solveable. The lower level holds some more
serious challenges:
- objects in midgard can be both members and collections. DAV will
have support for this thru advanced collections, ut this is currently
not implemented yet.
- Collections and members are not necesarily �compatible�with
peers.
It makes no sense to MOVE a style-member to a topic �collection
�- in DAV, the client controls the namespace. It can isse a request to
create object �X�. In midgard, you request a new object, but the
Midgard system decides what its �name�(ID) is going to be.
While mod_dav has a pretty good callback system, it does seem
to expect the repository backend to act like a filesystem.
Bye,
Emile
--
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]
