http://docs.zope.org/zope2/zope2book/ZopeArchitecture.html

Visting a URL of a Zope object directly is termed calling the object through the web

Zope had a much larger focus on Through-The-Web activities in its beginning. In recent years the Through-The-Web model has been discouraged for any kind of development and reduced to configuration tasks.

 

Zope provides the capability to manage users through the web via User Folders, which are special folders that contain user information.(check user folder?)

 

You can have more than one Zope running on your PC, but each has to have its own Instance Home, which is the path to specify here. This path is where Zope will later place its database files.

 

With the Zope binaries installed, you are now ready to create a Zope instance, which holds configuration and runtime data for a single Zope server process. This helps keep your own or third-party software separate from the main Zope source.

 

A successful Zope startup implies that Zope’s web server starts, which allows you to access the Zope management interface (ZMI) via your web browser.

 

/myzope/instance/bin/zopectl start to start a zope.

 

If you do need to have ZServer listening on low ports, you will need to start zopectl as the root user, and to specify what user ZServer should setuid() to. This can be done by setting the effective-user parameter in your Zope instances configuration file, residing in $INSTANCE_HOME/etc/zope.conf, and by making sure that the log and database files are writeable by this user.

 

 

difference between the objects stored in ZODB and the directorys...? answer 1: those are external methods of a zope.

 

===

Acquisition, on the other hand, stipulates that an object can additionally learn about its behavior through its containment hierarchy. In Zope, an object’s inheritance hierarchy is always searched for behavior before its acquisition hierarchy. If the method or attribute is not found in the object’s inheritance hierarchy, then the acquisition hierarchy is searched.

 

Acquisition allows behavior to be distributed hierarchically throughout the system. When you add a new object to Zope, you don’t need to specify all of its behavior, only the part of its behavior that is unique to that object. For the rest of its behavior, it relies on other objects. This means that you can change an object’s behavior by changing where it is located in the object hierarchy. This is a very powerful function that gives your Zope applications flexibility.

Acquisition is useful for providing objects with behavior that doesn’t need to be specified by their own methods or methods found in their inheritance hierarchies. Acquisition is particularly useful for sharing information (such as headers and footers) between objects in different folders as well. You will see how you can make use of acquisition within different Zope technologies in upcoming chapters.