Re: Autoexpanding ZIP archives?

Phillip Susi wrote:
> Is it really that hard to take a configuration directive to execute an
> external filter program?

How about this scenario?

RepositoryA requires FilterA for .OoO files
RepositoryB requires FilterB for .OoO files
RepositoryC has no filter requirements at all
...

The advantage with a wrapper is that each repository could have their
own wrapper. Client-side hooks which are not tied in some way to the
repository being accessed are going to be a serious problem (yes, you
could have a more complex config format which encapsulates all of that
information). It is *not* a simple problem to solve.

I get the feeling that most of the people arguing in favor of client
filters are *nix people. Subversion runs on multiple platforms and
there are multiple Subversion clients that are available (like
TortoiseSVN) where this kind of "exec a filter" model just doesn't map well.

I'm not directly arguing against _any_ client-side hook feature, merely
pointing out that adding it so you could have filename specific filters
without looking at the general case is putting the cart before the horse.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org