Jim Fulton wrote:
Not in principle. In fact, I would find it convenient for a particular
project. I doubt that anyone with access to that machine has time, \
although I can only speak for myself.
If I could get access, I'd make time ;-)
I think I used to have it, and I may well still do, but
Jim Fulton wrote:
At one point, enabling the 'http:' checkout gateway was a sure-fire
recipe for getting SVN's knickers in a twist, which is why we disabled
it. Or maybe that was ViewCSV.
Actually, it was BekeleyDB. :)
And Jens has fixed that now, iirc?
The main obstical was that it
Chris quoting Jim:
lame program for uploading keys, I find the ssh-based access
mechanism to be far more usable and secure.
Secure, maybe, but is it really worth it?
Usable? Don't agree, especially if you're trying to develop on Windows...
As a data-point, for the last year or 2, I've
Mark Hammond schrieb:
Chris quoting Jim:
...
I would support HTTP anonymous checkouts. I'm really against
writable HTTP checkouts because I consider the credentials
mechanism for HTTP access to be extremely lame.
whether SVN or not, I'm guessing any use of HTTP basic authentication
The ZODB allows to include the class (a reference to it)
into persistent references in order to avoid loading the object
state when a ghost object needs
to be created for the persistent reference.
For this to work, the class must not require arguments to __new__.
The ZODB checks whether the class
Mark Hammond wrote:
Chris quoting Jim:
...
whether SVN or not, I'm guessing any use of HTTP basic authentication
mechanism qualifies as extremely lame! I've no idea if this is what Jim
meant though :)
OK, for those not familiar with svn/HTTP authentication, as I understand it
you have to
Dieter Maurer wrote:
The ZODB allows to include the class (a reference to it)
into persistent references in order to avoid loading the object
state when a ghost object needs
to be created for the persistent reference.
For this to work, the class must not require arguments to __new__.
The ZODB
