Re: µsling 2.0 requirements (was: [RT] Shall we merge microsling into Sling?)

2007-12-20 Thread Michael Marth
Sounds great. This WebDAV module currently supports the Jackrabbit JCR repository, but Sling is meant to run with any JCR repository. OK, but can I add: switching the repository to another JCR repository is comparatively easy (i.e. does not require a recompile) (I like CRX's Repository

Re: µsling 2.0 requirements (was: [RT] Shall we merge microsling into Sling?)

2007-12-20 Thread Felix Meschberger
Hi, Am Donnerstag, den 20.12.2007, 16:48 +0100 schrieb Michael Marth: Sounds great. This WebDAV module currently supports the Jackrabbit JCR repository, but Sling is meant to run with any JCR repository. OK, but can I add: switching the repository to another JCR repository is

Re: µsling 2.0 requirements (was: [RT] Shall we merge microsling into Sling?)

2007-12-18 Thread Bertrand Delacretaz
On Dec 18, 2007 2:55 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote: ...Without going into the details, this means that usling is a pre-configured distribution of Sling. I'm wondering if we should stick with the name in this case?... Well, we could also try the webapp formerly known as µsling

Re: µsling 2.0 requirements (was: [RT] Shall we merge microsling into Sling?)

2007-12-18 Thread David Nuescheler
sounds great. regards, david On 12/18/07, Bertrand Delacretaz [EMAIL PROTECTED] wrote: Hi Wow, V2.0 already :-) We seem to agree on the need to merge µsling back into Sling, so I think it' be good to agree on the goals first - feel free to comment and expand on the following list of

Re: µsling 2.0 requirements (was: [RT] Shall we merge microsling into Sling?)

2007-12-18 Thread Felix Meschberger
Hi, I can only support these ideas because they bring an entry-level Sling using a subset of the same components as are used in Sling. Am Dienstag, den 18.12.2007, 14:44 +0100 schrieb Bertrand Delacretaz: Wow, V2.0 already :-) Makes sense, as the initial Apache Sling release will also be 2.0.