Bradley, James D. [Contractor] wrote:
>Greetings,
>
>I'm new to Subversion and this list, so forgive me if I'm being naive, but
>it seems to me the ideal solution to this problem would be some form of
>server-side pluggable content handlers. If the checkin/checkout/search/etc
>interfaces are abstracted, then we can create modules to handle the details
>of these operations for different file types, based on MIME type for
>example. The file type could be specified during initial checkin (if it's
>not obvious from the extension) and kept in the property list. Thus
>operations could be optimized for different file types, and new modules
>could be built and added dynamically to support new file types.
>
>This addresses fitz's concerns regarding tar wrappers and prefs setup, and
>eliminates William's security concerns of server-controlled client-side
>scripts. It would work well with the idea of opaque collections. I don't
>know if it qualifies as a "stunningly elegant solution"... but it seems like
>a decent idea to me...
>
>Or am I talking out of my rear-end??
>
Not quite, but... :-)
There's a policy involved here. It says that the server shall never,
ever try to second-guess the client, and it will not change the contents
of the files in any way. The server's one and only job is to store and
retreive data.
Fiddling with the contents on the server can lead to horrible, hard to
reproduce an even harder to debug problems.
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 25 22:25:12 2003