[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [corona-dev] A webdav "Repository"
|
Marcin:
Here is what I read on Apache about webdav
http://httpd.apache.org/docs/2.0/mod/mod_dav.html
Any location on the server where DAV is enabled should be protected by authentication. The use of HTTP Basic Authentication is not recommended. You should use at least HTTP Digest Authentication, which is provided by the mod_auth_digest module. Nearly all WebDAV clients support this authentication method. An alternative is Basic Authentication over an SSL enabled connection.
I thought we already had Apache available and it was just a matter of configuration to make webdav available. Is there this be a Jetty Servlet webdav we should use instead instead?
Regarding FTP - yes I think should eventually have an FTP client repository adapter. There is an Eclipse FTP client plugin we could probably wrap into a repository adapter. I thought we could use the experience Edyta is gaining from working webdav in Jackrabbit to get the webdav implemented quickly. Do you think FTP would be better to do first?
I thought the division was Page Views know how to handle content-type and Repository extension points handle access-type. So the viewers handle reading and display of files whereas repository adapters handle access to files. So many views still have to written but maybe not as many repository adapters.
Glenn Everitt
-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Marcin Okraszewski
Sent: Tuesday, December 12, 2006 6:01 AM
To: Corona development
Subject: Re: [corona-dev] A webdav "Repository"
Do you mean the Apache HTTP server with mod_dav, or some Java web
application that can be put into the Jetty servlet container within
Corona server? If the later, could you give some link?
I don't exactly understand what you mean by "The benefits would be we
would not have to create many small RepositoryAdapters for individual
files". We can have some abstract adapter that can talk with WebDAV, but
on top of that we have to write an adapter that is able to read the
content of the file exposed with WebDAV. So, one adapter that is able to
parse our team member xml file, the second one to something else. WebDAV
for me is just a way to retrieve and write content. But FTP server could
be used for this as well.
Marcin
Everitt, Glenn napisał(a):
> After talking with the Buckminster people, I started to implement the
> remote access to TeamMember.xml file as an example of how to create a
> simple RepositoryAdapter. As I am coding the example I keep thinking
> that the thing to do is to just implement a webdav based
> RepositoryAdapater so that properly authorized users (based upon our
> TeamMember file) can access files via webdav made visible through
> Apache web server configuration. Edyta has been working on webdav
> interface to Jackrabbit which involves determining the mapping from
> webdav commands to Jackrabbit JCR commands which aren't really
> documented (meaning it hard work to figure this out). This
> RepositoryAdapter I am proposing would use only existing webdav
> support. I believe we can use the eclipse webdav plugin that Edyta
> discovered for the client interface and we would need to configure
> Apache to start the webdav service as well as define a "Corona
> Repository Directory for files. The other issue is configuring the
> Apache HTTP Digest Authentication.
>
> The benefits would be we would not have to create many small
> RepositoryAdapters for individual files. I am expecting that
> Buckminster will start with 1 file and then add many files over time.
> We could reuse that the webdav RepositoryAdapter with the same
> repository descriptor. The RepositoryAdapter fetchResource api would
> specify the file name as the resource name. I think with Edyta's
> webdav experience the client RepositoryAdpater could be put together
> quickly. I don't know how much work configuring Apache webdav would be
> or how difficult it is to make this approach reasonable seamless and
> yet secure.
>
> Does anyone have any experience with Apache Server webdav
> configuration or security issues?
>
> Glenn Everitt
>
> The contents of this e-mail are intended for the named addressee only.
> It contains information that may be confidential. Unless you are the
> named addressee or an authorized designee, you may not copy or use it,
> or disclose it to anyone else. If you received it in error please
> notify us immediately and then destroy it.
>
>------------------------------------------------------------------------
>
>_______________________________________________
>corona-dev mailing list
>corona-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/corona-dev
>
>
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
