Cary O'Brien wrote:
I've done it this way:
http://www.zope.org/Members/otto/portfw
[snip]
How can this work? Won't Zope put a "base href=http://server:8080" tag
into the head of the document and mess things up? Won't you need
site-access to work around this?
-- cary
You're
Bill Anderson wrote:
[snip]
Hmm ... howzabout this for an idea, at least:
Since the Data.fs is appended to, and that your disconnected version
is canonical, why couldn't you basically look for the last common
transaction, and append all transactions in the canonocial to the
main
I've done it this way:
http://www.zope.org/Members/otto/portfw
It's also relatively easy to convince a hosting provider to add this, as
long as you have a dedicated IP address.
Perhaps I should have done a news item when I created this... seems a
lot of people have hacked around the issue is
One thing I considered doing was using 2.2's mountable databases for
something like this. Give each user their own database (possibly
without undo information) and use a cron job to check file sizes. If
you have root on the box, you could create users id's for each user and
use quota on the
Simon Michael wrote:
[snip]
4. could we auto-login with cookies like eg slashdot ? I'm never
logged in when I need to edit a wiki and doing so is quite
disruptive. And, or, make the login page auto-redirect back to where
I came from.
I'd like that, as well. Just make it a persistant
Works great for me.
Did you read http://www.zope.org/Members/4am/SiteAccess2/upgrading and
do the steps listed there?
The one thing I did have to change was my access rule. I had been using
the hack where you append /Z/ to manage interface URI's so they don't
get rewritten. What I had was
If you manage to find it, would you post a link to it?
Thanks.
-Otto.
Chris McDonough wrote:
Actually, there is a proposal on the table for something like this
in a Wiki I can't find going by the name of "QuorumBasedReplication"