Re: [Zope] Making Magic with Mirrowing Folders

15 Jun 2004


      Hi Dieter -
Sorry, I'm still slightly unclear.  Using the schema you described ...
The mirrowing folder is obviously set in the acquisition path of
application 1 in the context of language 1.
Is it's target supposed to be set to be one of it's child folders ..
MirrowTarget__ = "common" and this places
any child of common with a folder name matching any folder that is a
parent of application1 into the acuisition path or does this place only
the target, just common iteslf, into the path as if it's contents were
directly in the mirrowing folder?
Thank you for clarifying,
Gary

----- Original Message ----- 
From: "Dieter Maurer" <dieter@handshake.de>
To: "Gary Duke Speer" <gspeer@cortech.org>
Cc: <zope@zope.org>
Sent: Sunday, June 13, 2004 4:40 AM
Subject: Re: [Zope] Making Magic with Mirrowing Folders
...
Gary Duke Speer wrote at 2004-6-11 12:19 -0600:
...
I have been trying to configure Dieter's Mirrowing Folders Product.
Using both direct _dtml-var_ links and Shane's AquisitionUnderstander I
cannot see the product having any effect.  I suspect it is because I do
not understand either the product's intention or how to properly setup
the
mirrow link.
"Mirroring Folder" supports the following use case:
A multilingual site with multiple
  applications/subapplications/subsubapplications...
Each application (subapplication ...) contains language
  independent resources (business logic, common infrastructure,
  gluing scripts, ...) and language dependent resources
  (presentation, content).
All resources for an application are directly associated with
  this application; there is no further organisation based on e.g.
  type.
For these kinds of use cases, you would set up "MirroringFolder"
as follows:
MirroringFolder/
     common/ # mirrored by the mirroring folder
       application1/
         subapplication1/
...
       application2/
       ...
     language1/
       application 1/
       ...
     language2/
     ...
Note that Zope does not support optimally an organisation
based on types (like "Images", "SQL", ...).
Do not organize your resources like this for Zope.
Organize, instead by applications (subapplications, ...).
This lets take you optimal advandage from acquisition.
MirrowingFolder does not (or very limited) support organisation
by type.
Note further that MirroringFolder does its magic during
URL traversal. Do not expect any effect unless you
traverse through the folder.
-- 
Dieter