Hi,
On Nov 19, 2007 11:10 PM, Roy T. Fielding [EMAIL PROTECTED] wrote:
On Nov 19, 2007, at 11:57 AM, Jukka Zitting wrote:
Though, on a tangent, I'm wondering if we could achieve the same use
cases with just the existing URL-to-JCR-path mapping. [...]
The disadvantage is that it makes a
Hi,
On Nov 20, 2007 1:53 AM, Padraic I. Hannon [EMAIL PROTECTED] wrote:
I guess I am a bit confused as to what is wrong with
/path/to/document.pdf
/path/to/document.html
I'm most concerned about two things, one minor and the other more fundamental.
The minor issue is that . is a valid JCR
Hi,
On Nov 18, 2007 4:45 PM, David Nuescheler [EMAIL PROTECTED] wrote:
I think a .getNode() would be much less confusing and more direct.
If someone should ever need a getItem() or even a .getRawData()
i think we could always address that later.
+1 I would even go as far as questioning the
Hi,
Am Montag, den 19.11.2007, 11:01 +0100 schrieb Thomas Mueller:
x Sling applications using only 1 JCR Repository
Probably the main question is, are there any fixed paths?
This is basically supported. And yes, there are some fixed paths (at
least in microsling, but also in Sling). But the
Hi,
Am Montag, den 19.11.2007, 10:47 +0100 schrieb Juanjo Vázquez:
Accordingly, I´m wondering if Sling is intended to
support all the next situations:
1 Sling distribution = 1 application + 1 JCR Repository
This is probably the default, right ? So I assume this must be
supported.
1 Sling
