Unico Hommes schrieb:
Daniel Florey wrote:
Hi folks,
I've started a thread for discussions about architectural changes in Slide 3.0 some time ago. What about moving this to the Wiki to have a centralized point for further discussions?
Beside this I've thought about the following:
As Slide 3.0 will introduce some major changes that will lead to Slide level api incompatibilites, I'd vote for setting up a new CVS module for Slide 3.0 as tomcat is doing the same for major versions. This would give us the chance to set up a clean directory structure that reflects our increased wisdom.
As the Slide subprojects are big ones (server,clientlib, commandlineclient, testsuite, projector,...) it might also be a choice to split them into different cvs modules. What do you think about this?
This would lead to the question if we should try to shift Slide to apache top level (webdav.apache.org) to give the users a better understanding what Slide is all about and to simplify the access to the different subprojects. Remind that the testsuite, the client or projector are not tied to Slide, they work with every WebDAV-compliant server.
As stated in the subject of this mail, this are long term plans. But we should start to think about the way to go now as there is a lot of administrative work to be done to achieve this.
Personally, I would love to see a webdav TLP. As you note there is enough stuff in Slide to account for it. Regardless of whether or not we decide to push for a TLP I think it would be good to move to subversion. Many Apache projects already did the migration.
Regarding the evolution of the Slide webdav server, I think we should adopt jcrri to build version 3.0 on. This will also attract a lot of different people to the project and thus be a great community builder.
This would be great if jcrri would provide all requirements to build a WebDAV layer on top of it (including all the current drafts). As see slide as a bunch of java software related to WebDAV. If we could achieve this using jcrri I'd vote for it. Stefan (currently working on the jcrri) stated in his mails that there might be some problems regarding the content model.
We have to investigate, which api will match best (jsr-147 or jsr-170 or something totally different...)
Daniel
-- Unico
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
