Tags:
create new tag
, view all tags
Some interesting code has recently gone into the TWikiAlphaRelease to deal with mirrors. The change scripts e.g. attach & edit now have code to give an oops error if run on a MirrorSite. A few thoughts on this:

  • I think most of this could be done in less code in the initialize routine
    • If the requested script is a change script then fill in request and return code to calling script for an immediate return
    • I think much of the access control checks could also be done at this point
  • An alternative possibility is to redirect to the master site, which also avoids the need for disabling these items in view
  • It would also be good to make the disabiling features more general, the DrKW installation doesn't show options that aren't valid e.g. if you can't edit a topic, this option isn't given.

-- JohnTalintyre - 13 Jun 2001

Good idea about centralising access control checks. Any redirection to a central site should be configurable, as in some cases the mirror may be offline, e.g. on a laptop.

-- RichardDonkin - 15 Jun 2001

The code you have seen is work in progress / not usable at the moment. The idea is to have several sites where content gets mirrored between sites. There is no central site, but each web has a originating site where topics can be changed. Mirrored webs are not editable but should have a link to the topic on the originating site.

-- PeterThoeny - 16 Jun 2001

We've now got this setup, and working, and have now stopped calling our stuff being stored on a Twiki Server but more a Twiki Net... smile We're using the setup I describe in DataAndCodeSeparation and using rsync to do mirror the content in a low bandwidth manner.

Content is "owned" by a site rather than at a central site - which does complicate the mirroring slightly, but has the advantage that someone can own the content on a laptop, remote site, etc. As a result the links to the edit & attach URLs need manual (ick!) editing in the templates rather than using %EDITTOPIC% in the templates.

The way we've got it setup at the moment is content is pulled by the site that wants to mirror about once an hour, and authentication problems are handled by using one of apaches very nice authentication server access modules. This allows things like the access controls to work seamlessly throughout the (current 3) sites as well.

From a user's perspective it's nice and seamless - you want to mirror something across the Twiki net? Just attach it to your local Twiki server.

-- TWikiGuest - 17 Aug 2001

Edit | Attach | Watch | Print version | History: r10 < r9 < r8 < r7 < r6 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r10 - 2006-01-02 - PeterThoeny
 
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.