9. The Anatomy of Plone¶
In this part you will:
Learn a bit about the history and architecture of Plone.
Plone started as a extension for CMF, which is a extension for Zope. Python, ZODB, Zope, CMF, Plone, Volto ... -- how does all that fit together?
To store data Plone uses a database called
ZODB: A native object database for Python
There is no separate language for database operations like SQL
There is very little impact on code to make objects persistent
Object database != ORM
There is almost no seam between code and database.
import persistent class Account(persistent.Persistent): def __init__(self): self.balance = 0.0 def deposit(self, amount): self.balance += amount def cash(self, amount): assert amount < self.balance self.balance -= amount
Zope is a web application framework that Plone runs on top of.
The majority of Zope's code is written in Python, like everything else written on top of it.
It serves applications that communicate with users via http.
The great Version-Confusion
Plone was always based on Zope 2.x. Starting with Plone 5.2+ it uses Zope 4.x
Starting with Zope 4.0, the package is only called Zope (not Zope2 or Zope4)
Zope 3 is not a version of Zope but an ill-named rewrite of Zope 2 (sigh)
4.x is a mayor new release of Zope that supports Python 3 (among many other improvements)
Before Zope, web applications were often realized using plain CGI. An Apache web server would execute a script with the request data passed to it on standard input and as environment variables. The script would then just print HTML to the standard output. Apache returned that to the user. Opening database connections, checking permission constraints, generating valid HTML, configuring caching, interpreting form data and everything else: you had to do it on your own.
When the second request comes in, you have to do everything again.
Jim Fulton thought that this was slightly tedious. So he wrote code to handle requests. He believed that site content is object-oriented and that the URL should somehow point directly into the object hierarchy, so he wrote an object-oriented database, called ZODB.
The ZODB is a fully ACID compliant database with automatic transactional integrity. It automatically maps traversal in the object hierarchy to URL paths, there is no need to "wire" objects or database nodes to URLs.
This gives Plone its easy SEO-friendly URLs.
Traversal through the object database is security checked at every point via very fine grained access-control lists.
One missing piece is important and complicated:
Acquisition is a kind of magic. Imagine a programming system where you do not access the file system and where you do not need to import code. You work with objects. An object can be a folder that contains more objects, an HTML page, data, or another script.
To access an object, you need to know where the object is. Objects are found by paths that look like URLs, but without the domain name. Now Acquisition allows you to write an incomplete path.
An incomplete path is a relative path, it does not explicitly state that the path starts from the root, it starts relative to where the content object is -- its context.
If Zope cannot resolve the path to an object relative to your code, it tries the same path in the containing folder. And then the folder containing the folder.
This might sound weird, what do I gain with this?
You can have different data or code depending on your
Imagine you want to have header images differing for each section of your page, sometimes even differing for a specific subsection of your site.
You define a path
header_image and put a header image at the root of your site.
If you want a folder with a different header image, you put the header image into this folder.
Please take a minute to let this settle and think about what this allows you to do.
contact forms with different e-mail addresses per section
different CSS styles for different parts of your site
One site, multiple customers, everything looks different for each customer.
As with all programming magic, acquisition exacts a price. Zope code must be written carefully in order to avoid inheriting side effects via acquisition.
The Zope community expresses this with the Python (Monty) maxim: Beware the
9.3. Content Management Framework¶
CMF (Content Management Framework) is add-on for Zope to build Content Management Systems (like Plone).
After many websites were successfully created using Zope, a number of recurring requirements emerged, and some Zope developers started to write CMF, the Content Management Framework.
The CMF offers many services that help you to write a CMS based on Zope. Most objects you see in the ZMI are part of the CMF somehow.
The developers behind CMF do not see CMF as a ready to use CMS. They created a CMS Site which was usable out of the box, but made it deliberately ugly, because you have to customize it anyway.
We are still in prehistoric times here. There were no eggs (Python packages), Zope did not consist of 100 independent software components but was one big file set.
Many parts of Plone are derived from the CMF, but it's a mixed heritage. The CMF is an independent software project, and has often moved more slowly than Plone.
Plone is gradually eliminating dependence on most parts of the CMF.
9.4. Zope Toolkit / Zope3¶
Zope 3 was originally intended as a rewrite of Zope from the ground up.
Plone uses parts of it provided by the Zope Toolkit (ZTK).
The name was very unfortunate since it was in no way compatible with Zope 2
Unfortunately, only few people started to use Zope 3, nobody migrated to Zope 3 because nobody knew how.
But there were many useful things in Zope 3 that people wanted to use in Zope 2, thus the Zope community adapted some parts so that they could use them in Zope 2.
Sometimes, a wrapper of some sort was necessary, these usually are being provided by packages
five namespace. (Zope 2 + Zope 3 = "five")
To make the history complete, since people stayed on Zope 2, the Zope community renamed Zope 3 to Bluebream, so that people would not think that Zope 3 was the future.
It wasn't anymore.
9.5. Zope Component Architecture (ZCA)¶
The Zope Component Architecture, which was developed as part of Zope 3, is a system which allows for component pluggability and complex dispatching based on objects which implement an interface (a description of a functionality).
It is a subset of the ZTK but can be used standalone. Plone makes extensive use of the ZCA in its codebase.
Pyramid is a Python web application development framework that is often seen as the successor to Zope.
It does less than Zope, is very pluggable and uses the Zope Component Architecture “under the hood” to perform view dispatching and other application configuration tasks.
You can use it with a relational Database instead of ZODB if you want, or you can use both databases or none of them.
Apart from the fact that Pyramid was not forced to support all legacy functionality, which can make things more complicated, the original developer had a very different stance on how software must be developed. While both Zope and Pyramid have good test coverage, Pyramid has good documentation; something that was very neglected in Zope, and at times in Plone too.
Whether the component architecture is better in Pyramid or not we don't dare say, but we like it more. But maybe it's just because it was documented.
Definition of the PYTHON_PATH makes up most of the
bin/instance script's code.
Look at the package list (and maybe also the links provided in the respective sections of this chapter).
Try to identify 3 packages that belong to Zope 4, 3 packages from CMF, 3 Zope Toolkit packages and 3 packages from the ZCA.
Zope 4: Zope, ZODB, Acquisition, AccessControl, ...
CMF: Products.CMFCore, Products.CMFUid, Products.CMFEditions, ... Products.DCWorkflow doesn't fit the pattern but is a very important part of the CMF
ZTK: zope.browser, zope.container, zope.pagetemplate, ... You can find a complete list here
ZCA: zope.component, zope.interface, zope.event
9.9. REST API¶