is a recognizably outdated way.)Em Zope 2 Book, relata:"One of the most notable differences between the original Zope2 approach and todays best-practices is in the way you develop applications with Zope2. The original Zope2 approach has focussed on a Through-The-Web (TTW) development model. You would create your entire application and manage your data through the same browser interface and store everything transparently in the same database. This model has worked very well in the beginning of the web as many dynamic websites have been rather simple and specialized projects.Over the years websites have grown their requirements and often turned into development projects of a considerable size. Today websites are understood as applications in themselves and need an approach which is no longer compatible with the TTW approach of the early Zope2."Conceito de aquisicao do Zope 2 (Concept of Acquisition)"One more prominent aspect of Zope is acquisition, whose core concepts are simply that:Zope objects are contained inside other objects (such as Folders).Objects can "acquire" attributes and behavior from their containers."Diferenca entre heranca e aquisicao: "Inheritance stipulates that an object can learn about its behavior from its superclasses via an inheritance hierarchy. Acquisition, on the other hand, stipulates that an object can additionally learn about its behavior through its containment hierarchy. In Zope, an objects inheritance hierarchy is always searched for behavior before its acquisition hierarchy. If the method or attribute is not found in the objects inheritance hierarchy, then the acquisition hierarchy is searched.""Acquisition is not limited to searching a containment hierarchy: it can also search a context hierarchy. Acquisition by context is terribly difficult to explain, and you should avoid it if at all possible.""Acquisition allows behavior to be distributed hierarchically throughout the system.""Acquisition is a mechanism in Zope for sharing information among objects contained in a folder and its subfolders."Separar camada de apresentacao e de logica (Keep presentation and logic separate)"Zope encourages you to keep your presentation and logic separate by providing different objects that are intended to be used expressly for presentation. Presentation is defined as the task of dynamically defining layout of web pages and other user-visible data. Presentation objects typically render HTML (and sometimes XML)." (fonte) Prefira ZPT a DTML (ZPT is better than DTML)Motivo 1: DTML e velho. "an older version of a presentation facility included, which is called Document Template Markup Language or short DTML."Motivo 2: DTML nao faz boa separacao entre camada de apresentacao e camada responsavel pela logica: "There is a major problem with many languages designed for the purpose of creating dynamic HTML content: they dont allow for separation of presentation and logic very well. For example, tag-based scripting languages, like DTML, SSI, PHP, and JSP, encourage programmers to embed special tags into HTML that are, at best, mysterious to graphics designers who just want to make the page look good and dont know (or want to know!) a lot about creating an application around the HTML that they generate. Worse, these tags can sometimes cause the HTML on which the designer has been working to become invalid HTML, unrecognizable by any of