[Zope] Structuring Zope objects (Actors?) for global access

[Tony McDonald]

I was wondering what the best practice is for allowing access to Zope 
objects from anywhere in the hierarchy?

I intend to be able to put methods such as 'upload', 'mcq' and 'edit' 
at the end of URLs and have them do the appropriate things to that 
object at that URL (if it's permissable). eg 
/guides/s1ot/e47/e56/edit will edit the XML representation of a part 
of a study guide and /guides/s1ot/theme3/mcq will show all multiple 
choice questions associated with a specific section of the course.

Normally I would put the objects at the top level of the tree, but 
having seen mentions made of UML and Actors on the list, I decided to 
look into that a bit more. It seems that you should do something like 
/guides/s1ot/e46/e56/Actors/edit and /guides/s1ot/theme3/Actors/mcq, 
having first put your methods etc into a folder called Actors at the 
top level of the hierarchy. Is this the 'Zopish' way of doing things? 
I mean, is this the proper way to manage these objects? (I'd like to 
get these fundamentals sorted out before embarking on the big stuff!).

TIA
tone.
------
Dr Tony McDonald,  FMCC, Networked Learning Environments Project 
http://nle.ncl.ac.uk/
The Medical School, Newcastle University Tel: +44 191 222 5888
Fingerprint: 3450 876D FA41 B926 D3DD  F8C3 F2D0 C3B9 8B38 18A2