On 5/3/2010 1:43 PM, Grégory Joseph wrote:

On May 3, 2010, at 22:28, Ruben Reusser wrote:
On 5/3/2010 1:03 PM, Grégory Joseph wrote:
Hi Ruben,

On May 3, 2010, at 21:39, Ruben Reusser wrote:

I noticed webdav seems to have some problems with windows,

Does it ? What/where ? Can you elaborate on what problems you're referring to?


well, out of the box windows integration without an additional tool is not so 
great in magnolia when I tested the last time - is it better now? Can I use a 
windows share?
Ha! THAT's what you meant. But as far as I recall, the issue there is that 
Windows does not respect the WebDAV protocol properly; does Milton work around 
that ? Do you have any pointer about this ?
As far as using WebDAV-without-additional-tool on Windows, I also seem to 
recall that this was highly dependent on which Windows version you're using; 
some of them being more WebDAV-friendly than others ...

:-) from the mitlon website:

*What is it compatible with?*

Its been tested and works well with Windows XP, Linux and MacOS. Note that webdav support in Windows Vista has issues and users might need to download a patch. The two main office applications, Open Office and MS Office, also have build in webdav support and both have been tested and work well with Milton.

http://milton.ettrema.com/compat/index.html

so I was wondering if it would be better to do a webdav implementation with 
milton http://milton.ettrema.com/index.html instead of the current webdav 
implementation.

Maybe. But that'd mean rewriting our module ;) I don't know Milton at all, and it could 
be that they have a very simple API to do mappings similarly to what we have in our 
current WebDAV module (we had to resort to a few hacks here and there, to plug 
"our" logic in Jackrabbit's WebDAV API, but now it seems that implementing a 
custom WebDAVMapping for Magnolia should be fairly straightforward for modules/workspaces 
which don't have one yet)
Milton has a nice API to plug your own resources into it. So it should be a 
breeze to write it :-)
Well, at first sight, the Jackrabbit API seemed nice too. And it IS nice, it 
just wasn't *exactly* what we needed. But thanks for the pointer, we'll try to 
have a look one of these days; or you should too. I'm pretty sure if you had a 
piece of code to convince us, that would help ;)


If time permits we'll try to do a sample for this integration :-)

http://milton.ettrema.com/guide/index.html


     Resource API

The Milton jar is designed to be a protocol handler. It simply interprets the HTTP protocol (with webdav extensions) and portrays it as a series of java interfaces.

Milton is agnostic about the nature of your data. You simply implement the interfaces needed for it to locate your resources, and those resources.

Milton is also agnostic about your runtime container. It was specifically designed to not depend on the Servlet API. Instead, a seperate library called MiltonServlet provides that integration. But Milton could equally be used from any other web container such as SimpleWeb or xLightWeb

As part of not depending on the Servlet API, Milton has its own support for Filters <http://milton.ettrema.com/reference/Milton/javadoc/com/bradmcevoy/http/Filter.html>.

Webdav has no concept of sessions, and webdav clients usually don't implement any of the session mechanisms used by browsers. So Milton has no explicit support for sessions or cookies. However, if you use MiltonServet you can access the underlying request and response objects by casting the request to ServletRequest <http://milton.ettrema.com/reference/MiltonServlet/javadoc/com/bradmcevoy/http/ServletRequest.html> and calling getRequest

Cheers,

-g
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to:<[email protected]>
----------------------------------------------------------------


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to