On Tue, 23 Nov 1999, Greg Stein wrote:
> > You can tell a WebDAV enabled server to create a member
> > 'index.html' at URI '/user/emile', but that's not how Midgard works,
> > where you request a new object at URI '/user/emile' and get handed it's
> > ID in return.
>
> Hrm. This just came up on the DAV Working Group list about a month or so
> ago. There were some suggestions for how to handle this. I don't recall
> them right now :-( I seem to recall something about returning a Location:
> header from a PUT or a MKCOL to indicate where the thing was actually
> created/stored. Another suggestions was to create a "binding" between the
> URI that the author used and the "true" URI (the ID-based one).
We've found a workaround for this which will allow DAV clients to
create named objects and have midgard do the right thing.
But never fear, I've come up with another issue to keep things
challenging.
Many midgard objects include multiple fields whose purpose is to hold
HTML snippets to be combined into a page to be sent to the client.
Most of these snippets will not validate as HTML (as they will
not have dtd, head or body tags). These fields are the things
we would like to see editable by a DAV enabled HTML editor.
So the question is: how to handle objects (members) where the
content is in fact broken up into multiple properties? What
will get us the best cooperation with the (few ATM) DAV
enabled HTML editors?
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]
