On Wed, Oct 15, 2008 at 11:24 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
Seen that, and I think we should have a separate method here, as we
don't want a session ID in Sling apps ;-)
do we ? actually, what we say is don't use HttpSessions.
But if an application still wants to use an
Repository Ping thread may terminate without any traces in the log files
Key: SLING-698
URL: https://issues.apache.org/jira/browse/SLING-698
Project: Sling
Issue Type:
Bundles should be installed, updated started one after the other
Key: SLING-699
URL: https://issues.apache.org/jira/browse/SLING-699
Project: Sling
Issue Type: Improvement
enhance ResourceResolver#findResources() signature to support typing
Key: SLING-697
URL: https://issues.apache.org/jira/browse/SLING-697
Project: Sling
Issue Type:
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 POST
[
https://issues.apache.org/jira/browse/SLING-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12640120#action_12640120
]
Carsten Ziegeler commented on SLING-699:
I synchronized the two methods in question
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.
in some cases, sling should be put in charge to create something new
and unique without the
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 differentiating between create
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
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
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
parameters or query parameters...
...
Speaking of
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...
also there is a quite
[
https://issues.apache.org/jira/browse/SLING-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12640443#action_12640443
]
Carsten Ziegeler commented on SLING-697:
(the method name should actually be
13 matches
Mail list logo
