You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Stuart Douglas <st...@baileyroberts.com.au> on 2007/07/13 09:32:52 UTC

WEBDAV for use in an office

In the subversion book it talkes about using webdav file systems in an office environment, to version all important files.I really want to implement something like this were I work, as we really cannot have any client realated information lost. The caveat is that if a user uses word to open files on the webdav files it will create temporary files, that will stick around to eternity. I have two possible solutions in mind, and I was after some feedback as to if either of them will actually work:
 
1) Every so often run svndumpfiler to filter out the temp files. Although I am not sure if this will work, because I did not see anything to suggest svndumpfiler supports the nessesary wildcards in the exclude path.
 
2) User mod_rewrite to redirect all temp file requests to a seperate non-versioned filesystem. This is the one I prefer, because it will be interesting to set up, but I am not sure if it will work. The issues I see are:
 
 - temp files will not show up in the file manager, however direct read/write requests for the filename will still work.
 - the temp files will have to be stored in some funky way, either all in the same directory or on a custom fuse filesystem that automatically creates directories (probably the first option)
 
Does anyone know if either of these would work? I am leaning more towards option 2 but I am not sure if it will cause problems down the track.
 
Stuart
   

RE: WEBDAV for use in an office

Posted by Jason Winnebeck <jp...@rit.edu>.
________________________________________
From: Stuart Douglas [mailto:stuart@baileyroberts.com.au] 

In the subversion book it talkes about using webdav file systems in an office environment, to version all important files.I really want to implement something like this were I work, as we really cannot have any client realated information lost. The caveat is that if a user uses word to open files on the webdav files it will create temporary files, that will stick around to eternity. I have two possible solutions in mind, and I was after some feedback as to if either of them will actually work:
 
...
 
2) User mod_rewrite to redirect all temp file requests to a seperate non-versioned filesystem. This is the one I prefer, because it will be interesting to set up, but I am not sure if it will work. The issues I see are:
 
------------

I doubt that the second approach will work because if the Office or other application does a list to look for "locking" files, it won't see them if you are transparently redirecting URLs with certain wildcards. So I'm guessing that breaking the ability to list files would also break the ability for the applications to work properly.

Jason Winnebeck

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org


Re: WEBDAV for use in an office

Posted by Toby Thain <to...@smartgames.ca>.
On 13-Jul-07, at 6:32 AM, Stuart Douglas wrote:

> In the subversion book it talkes about using webdav file systems in  
> an office environment, to version all important files.I really want  
> to implement something like this were I work, as we really cannot  
> have any client realated information lost. The caveat is that if a  
> user uses word to open files on the webdav files it will create  
> temporary files, that will stick around to eternity. I have two  
> possible solutions in mind, and I was after some feedback as to if  
> either of them will actually work:
>
> 1) Every so often run svndumpfiler to filter out the temp files.  
> Although I am not sure if this will work, because I did not see  
> anything to suggest svndumpfiler supports the nessesary wildcards  
> in the exclude path.
>
> 2) User mod_rewrite to redirect all temp file requests to a  
> seperate non-versioned filesystem. This is the one I prefer,  
> because it will be interesting to set up, but I am not sure if it  
> will work. The issues I see are:
>
>  - temp files will not show up in the file manager, however direct  
> read/write requests for the filename will still work.
>  - the temp files will have to be stored in some funky way, either  
> all in the same directory or on a custom fuse filesystem that  
> automatically creates directories (probably the first option)
>
> Does anyone know if either of these would work? I am leaning more  
> towards option 2 but I am not sure if it will cause problems down  
> the track.

A bit OT, but have you considered using something other than bl**dy  
Word as a an editing interface? A versioned wiki such as TWiki  
(http://twiki.org/) gives you collaborative work with automerged  
changes (a bit like Svn); hyperlinks (it's 2007, after all);  
hierarchy; browser based, so you get server based storage and remote  
access for free; plugins; friendly UI; etc, etc, etc.

Then there are dedicated DMS such as KnowledgeTree...

--Toby

>
> Stuart
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org