[Zope-dev] RE: Object links/references

Niels Mache mache@struktur.de
Wed, 20 Mar 2002 14:02:15 +0100


This is a multi-part message in MIME format.
--------------C9B07D363FC16C67114A2B8D
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Brian Lloyd wrote:
> 
...
> I can easily imagine that "right" behavior of a link if
> your main goal is to avoid 404s will _not_ be right if
> you are using the link in other ways. For example, if you
> went to a URL that had been moved, what is the right
> "context" that it should render itself in? I highly suspect
> that the right context is the place that it was moved to,
> rather than the context where the link lives (redirect
> semantics). That is basically the opposite of another
> possible usage of a link, where you would want to use the
> link to "virtually include" an object into a different
> context.
> 
> I submit that trying to do both is too complex
> and probably too insecure as well (as managers of security
> would have to evaluate N possible security scenarios, most
> of which are not readily visible to them at the time they
> are setting up security).
> 
> I think that the "RedirectObject" approach could sidestep
> all of these issues and provide an incremental step while
> still solving your problem.
> 
> Brian Lloyd        brian@zope.com
> V.P. Engineering   540.361.1716
> Zope Corporation   http://www.zope.com
> 
> _______________________________________________
> Zope-Dev maillist  -  Zope-Dev@zope.org
> http://lists.zope.org/mailman/listinfo/zope-dev
> **  No cross posts or HTML encoding!  **
> (Related lists -
>  http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope )


With the icoya CMS, we implemented a similar "Resource"-/"Relay" object approach to overcome the difficulties described above. 
Resource objects are the containers (Zope objects) for content objects (located in the ZODB, Filesystem or databases). Beside the function as 
a storage container "Resources" implement versioning, languages, link bases and other features. To get Resources published, we introduced "Relay" objects. 
The "Relay"-object publish the content of a "Resource" in a defined manner i.e. style, variant, version, language, etc.. Furthermore the Relay can be used for  
dynamic folders, personalization and workflow. We have good experience with this approach, but at the beginning of our work we had to solve the performance penality that arose with the multiple indirection of the content. 


-- 
Niels Mache, Dipl. Inform.        
        
Chief Executive Officer
struktur AG             Fon.:  +49 (0)711 896656 53
Junghansstr. 5          Fax.:  +49 (0)711 896656 10
D-70469 Stuttgart       eMail: mache@struktur.de                    solutions for
Germany                 Web:   http://www.struktur.de            digital business
--------------C9B07D363FC16C67114A2B8D
Content-Type: text/x-vcard; charset=us-ascii;
 name="mache.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Niels Mache
Content-Disposition: attachment;
 filename="mache.vcf"

begin:vcard 
n:Mache;Niels
tel;fax:+49 711 896656 10
tel;work:+49 711 896656 53
x-mozilla-html:FALSE
url:www.struktur.de
org:<img src=http://www.struktur.de/logo/struktur.gif><br>struktur AG
adr:;;Junghansstr. 5;Stuttgart;Baden-Wuerttemberg;D-70469;GERMANY
version:2.1
email;internet:mache@struktur.de
title:CEO
fn:Niels Mache
end:vcard

--------------C9B07D363FC16C67114A2B8D--