[
https://issues.apache.org/jira/browse/SLING-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708831#action_12708831
]
Julian Reschke commented on SLING-967:
--
More implementation support:
* Xythos D
Bertrand Delacretaz wrote:
On Mon, Apr 20, 2009 at 5:45 PM, Carl Hall wrote:
Are node properties viewable/changeable through webdav access to a JCR repo?
Not AFAIK, WebDAV is about files...I *think* there's an enhanced
WebDAV component in Jackrabbit that allows for some additional JCR
remotin
David Nuescheler wrote:
for known resources this is the case... and everybody is welcome to do
that.
Sure; in *that* case of course PUT is right...
...and of course that works aswell ;)
except for that it is a pain to impossible to get a browser to do that.
think of file uploads for example...
Julian Reschke wrote:
...
So my answer is: we currently use xyz/* as a workaround, to
differentiate between "create" and "modify" when working with today's
browsers as clients.
One could imagine other ways to hack it into the URL, such as path
param
Bertrand Delacretaz wrote:
On Thu, Oct 16, 2008 at 5:14 PM, David Nuescheler <[EMAIL PROTECTED]> wrote:
...anyway, in hind-sight the /xyz/* for the POST is probably not ideal
and in my mind should
be deprecated in favour of /xyz/ with a trailing slash
The problem with not using xyz/* is di
David Nuescheler wrote:
Out of curiosity: why not just POST to the location? That seems to be more
in sync with how POST is defined in HTTP...
for known resources this is the case... and everybody is welcome to do that.
Sure; in *that* case of course PUT is right...
in some cases, sling shou
Hi,
I was just looking at the sling-in-15min tutorial, and came across the
section "Let Sling generate the path of a newly created node", which
describes using POST and "*" as last path segment...
Out of curiosity: why not just POST to the location? That seems to be
more in sync with how POS
