Data.fs.in0100644000077000001200000022327007232403277012024 0ustar stefanadminFS21)*ϱ(#p)*ϱ({(cAccessControl.User UserFolder qNtq.}qUdataq(U q(UBoboPOS.PersistentMappingqUPersistentMappingqtqtqQs. )*ϱ(=(cPersistence PersistentMapping qNtq.}qU _containerq}qs.#)*o;p amos/manage_importHack)*o;/|(cOFS.Document Document qNtq.}q(U__name__qUstandard_html_footerqUglobalsq}qUrawqUqU_varsq }q u.!)*o;/(cOFS.Document Document qNtq.}q(UtitleqUqUrawqT

An exiting new development being worked on for Zope is The Lever. The Lever will give Zope web application developers the ability to crank out and reuse their applications. Zope applications run the gamut of being just folder and document objects to complex data driven applications with pluggable brains and external methods. The lever will enable you to create such an application as a drop-in object. If you use a Tabula or Aqueduct and had a few reports and submission forms to create a shopping cart application for example, it could then be levered and dropped in anywhere as a Shopping Cart object.

qUglobalsq}qU__name__q U dtContentq U_varsq }q u.")*o;/-(cOFS.Document Document qNtq.}q(UtitleqUqUrawqT

Zope enables "stupid" data to become smart. Aqueduct gives smarts to relational data, Tabula gives it to desktop-based data (such as DBF files). While Aqueduct's data is external to Zope, Tabula brings its data inside. Besides speedy searches and flexible reports, Tabula adds intelligence to its data through computed fields, hierarchies and acquisition, plus all the features of DTML Scripting, especially direct querying.

qUglobalsq}qU__name__q U dtContentq U_varsq }q u.#)*o;/(cOFS.Document Document qNtq.}q(UtitleqUqUrawqT.

Sometimes DTML Scripting is not enough to get the job done. Getting into a full featured unrestricted language to extend the application at hand is what is needed. Enter External Methods. External Methods are written in Python and, like Pluggable Brains, have full access to all of the modules available for it. External Methods are natural extensions for Zope objects and are an easy way to interact with other system resources, like already existing Python modules, shell scripts, COM objects, and more. The possibilities are endless!

qUglobalsq}qU__name__q U dtContentq U_varsq }q u.$)*o;/(cOFS.Document Document qNtq.}q(UtitleqUqUrawqT|

With Zope and Aqueduct, you can make stupid data "smart". Pluggable Brains turn flat records returned from Aqueduct Database Methods (SQL Queries) into intelligent objects. These objects benifit from all the Python and Zope object technologies, including inheritence and acquisition, and have full access to the large suite of modules available in Python and Zope.

qUglobalsq}qU__name__q U dtContentq U_varsq }q u.%)*o;/(cOFS.Document Document qNtq.}q(UtitleqUqUrawqT

Zope's DTML is more than just a variable insertion and batch processing language. It also exposes a powerful expression language. While this expression language can be used to compute variables and text complex conditions on the fly, it can also be used to directly call methods on Zope objects. This powerful feature, referred to as DTML Scripting is the first level of advanced web application development in Zope. It is editable through the web, secure, and flexible enough for many applications.

qUglobalsq}qU__name__q U dtContentq U_varsq }q u.)*o;/ (cOFS.Document Document qNtq.}q(UrawqU
qUglobalsq}qU__name__qU dtcTemplateqU_varsq }q u.-)*o;/(cOFS.Document Document qNtq.}q(UtitleqUqUrawqTA

Sessions are a form of a long running transaction in Zope. Sessions allow the site to be worked on live without affecting its normal use. Only users who have joined a session to work on the site can see the changes being made. Everyone else won't see the changes until the session is saved. Sessions can span minutes or weeks, depending on the job.

There are numerous advantages to Sessions over some other means of site editing. The main advantage is the fact that you are modifying a live site, instead of working on a mirror copy of the site only to discover minor conflicts when you move it onto the live site. Sessions let you catch and fix errors that often happen when doing both major and minor overhauls such as broken links before your users do.

qUglobalsq}qU__name__q U dtContentq U_varsq }q u..)*o;/z(cOFS.Document Document qNtq.}q(UtitleqUqUrawqT

One of the main features of Zope's object database is its ability to Undo actions. This is not your typical undo found in text editors, spreadsheets, and other desktop applications. Made a change in some DTML that you didn't like? Wish you hadn't deleted those three images? Realize you uploaded the wrong file object? Clicking on the Undo tag (found on most Zope folderish objects, along with a few others) can help you. Since Zope is based on an object oriented database that stamps times on transactions (changes) to the system, Undo is a robust and solid benefit of this technology.

It also works with sessions. While you can discard changes made in a session instead of saving them, you might do some work in a session and make it public only to find out it's not as good as you thought. Since the session is saved as a single transaction, you can undo a massive amount of changes in one click. Be careful though - there is no redo!

qUglobalsq}qU__name__q U dtContentq U_varsq }q u./)*o;/(cOFS.Document Document qNtq.}q(UtitleqUqUrawqT

Another significant feature of Zope that comes from its web-to-objects philosophy is its entirely through the web management. A Zope is like its own little file system (but smarter, see Integrated object database above), and a web browser is its navigation and management interface. Combined with Zope's security options, this makes maintainence an anywhere-in-the-world task. Want to hand management of an area of the site off to someone else? Add a user folder to the folder you want to give them access to, make a user object with a name and a password, and tell them the URL to go to. If they have a browser that supports frames, they now have access. No setting up FTP and Telnet acounts. No requiring them to download and learn another client program. No having to deny users access because there's no client support for their particular operating system.

Zope's management interface is intuitive and simple. The left frame contains a tree of folderish objects (objects that can contain other Zope objects) for navigating to different points. The right frame is the workspace for the objects which uses a tabbed-style interface (a row of links across the top) for switching between different views and management options for an object. And it's fast loading due to its use of simple non-flashy images (which are less bulky and distracting) and light frame and table use. It uses standard HTML as much as possible to ensure the widest browser support without sacrificing usability. If you haven't done so already, check it out!

qUglobalsq}qU__name__q U dtContentq U_varsq }q u.0)*o;/(cOFS.Document Document qNtq.}q(UtitleqUqUrawqT7

At the heart of Zope is an integrated object database. This database mirrors the URL used to access objects, and behaves like a file system. The neat trick, however, is that these are intelligent objects, not dumb files. Information can be shared easily and dynamically across folders and documents and other Zope objects without the need to batch process every file in the system to accomodate a small change, say in a header or footer.

These objects can be "dropped in" at any time and anywhere. Out of the box Zope comes with support for some already common objects such as folders, images, arbitrary files, and documents. These objects, through use of folder properties, acquisition, and DTML (Zope's Document Template Markup Language) already give you enough to make a dynamic smart site using objects similar to what is used with static, "dumb" means of publishing.

But there's more. Out of the box Zope also comes with support for User Folders for managing access at any level of the site (and all Zope objects have configurable security attributes). There are also Session objects which allow the entire site or portions of the site to be modified live without affecting normal use of the site. Only users that have joined the session can see the changes until they're commited to the main database. Lastly, there are MailHost objects for configuring access to SMTP servers for use with the DTML sendmail tag. These objects, along with others available seperately, may be combined together in any fashion to achieve the results you want. Database integration, discussion groups, desktop database publishing mechanisms are all examples of some of the other objects available for use on the Zope platform.

Furthermore, this object database is transactional, meaning that only succesful changes will be commited to the database. It supports multi-level Undo, allowing the state of objects to be rolled back to previous versions.

qUglobalsq}qU__name__q U dtContentq U_varsq }q u.1)*o;/`(cOFS.Document Document qNtq.}q(UtitleqUqUrawqT

An added benefit of Zope's web-to-object mapping is that URL's address objects directly and most importantly make sense. Instead of addressing an object with a URL like:

/blu/347FGNNFUY2387H49YH796YY@874374NN.U897632S1?form_id=309823&action=nameForm&pid=438095739

You can use a URL like

/blu/forms/nameForm?form_id=309823

This calls the method (or Document) nameForm on the object forms contained by the object blu, and passes the parameter form_id to the method. This is more in step with traditional file-based publishing which is a hierarchy of folders/directories containing HTML documents. But now, the folders and documents have brains. And those brains don't tax yours by forcing you to manage long and ugly object access keys. So using a regular URL you can communicate with any object in the system directly. All through a regular web browser.

qUglobalsq}qU__name__q U dtContentq U_varsq }q u.2)*o;/(cOFS.Document Document qNtq.}q(UtitleqUqUrawqT-

Part of Zope's security model is based on the User Folder At any step in a URL, you can add a UserFolder for that customer. This is their part of the URL and the UserFolder holds their admin folks. They, in turn, can create sub-URLs and add UserFolders beneath. Have you lost control? No, because anyone allowed above can get in below. Moreover, if the customer goes away, you delete their URL and all of their users, their customer's users, etc. go as well.

To the browser, Zope uses standard HTTP Authentication. Not only does this eliminate the hassle of making and maintaining an HTML form based login screen, but it also avoids the hassle of tracking an authenticated user through cookies. Furthermore, the information exposed to DTML allows you to write documents that can show or not show certain portions based on the authentication roles of a user. Lastly, Zope's security model takes extra care to ensure that users deep down in the hierarchy cannot affect or steal from above without the authorization to do so.

qUglobalsq}qU__name__q U dtContentq U_varsq }q u.4)*o;/(cOFS.Image Image qNtq.}q(UsizeqM U content_typeqU image/gifqUdataq(U5q(U OFS.ImageqUPdataq tq tq QU__name__q Udatasharing1.gifq UtitleqUdatasharing figurequ.5)*o;/ $(cOFS.Image Pdata qNtq.}qUdataqT GIF89af3̙f3f3ffffff3f3333f333f3f3̙f3̙̙̙̙f̙3̙ffffff3f3333f333f3̙f3̙̙f3̙f3ff̙ffff3f33̙33f333̙f3ffffff3ffff̙fff3fffffff3ffffffffffff3fff3f3f3f3ff33f3ffffff3f3333f333333̙3f3333333f3333f3f3f3ff3f33f33333333f333333333f333f3̙f3f3ffffff3f3333f333f3wUD"wUD"wUD"ݻwwwUUUDDD""",H*\ȰÇ#JHŋ3N 1Ə C|hEGǒʗȜ93aɓ8;)O`mHxd 'O 8则{ճ'HiY/Wؠ# w p# 2nY+]W.sU]uڹOnGrMk#uq&8{5߀FxZK%s f*G|"h(,0xN2HRV)ٸb}2٤NXbj!J[aǚ}HdYIuQJ L:Q\-Y%y$fDԬCoF9@]nf%mNYjh r۝X9P if9)n(YFכ}ti::>j"*jy穰ƚd L8=} LS@ PJԥX$R'0Rb!|j0'Up"u!iI2wFj9ۢU$q )kl 0tWbT/•}g`wVb S!y*pk 48PIֺmE ʶI$ʫNT\=@$fܼfQR2hlJ'+*ѫΊݿRV?6UZ38Mlw^1fu,)_96 BiQJյ^ kZƱ9M݄o{Rm+[Q:ΩD[|Kܪ7#PW|1eIcbP1Jk])qYяWd2~dSowhF[yȀlLj0|S>ܵoL:+9H&qlM0 Ua\lp3S/rjfG:f.܍tkCM4'2אN>F9.֟K&f>l±X쵰Mb;xagt[h"wYE#wmg6d 2ۉ?{Wo(`!n/х2}]Yrf7c[2p;qs.3)*o;/(cOFS.Document Document qNtq.}q(U__name__qU dtContentqUglobalsq}qUrawqT

Problem: You have a common footer that you want on every page in your site. Well, not every page. There's one folder that needs a slightly different footer, but only that folder and its subfolders need it. Another problem: in that footer you want to have a feedback button to send email to someone about the site, but that someone can change and may need to be different in certain folders, and go unaffected in others. Solution: Acquisition!

Think of Acquisition as a sort of run-time inheritence (for the object savvy). Another way of looking at it is Environmental inheritence. When you're at work, your phone number is different than your phone number at home. You're the same person in both places, but your phone number changes depending on where you are. You acquire it from your environment. Acquisition is the same thing. Let's show how this is being used in the Objects section of this QuickStart.

Data Sharing Tree

You'll notice that every item in this tree that expands into content is indented in the tree properly and closes with a horizontal rule. While every document could have had a closing <HR> added at the end of it by hand, what if suddenly we decided to change the width of the rule or set it to noshade? Or even wanted to change with a different element such as an image? We'd have to go into and change each document by hand. Unacceptable. Instead, we use Acquisition. In the Outline (1) folder there is a document dtcTemplate. dtcTemplate is used to render the content sections (also known as leaves) of the tree you're viewing. The actual contents of the leaves are defined much further below. This section is defined in DataSharing (2), and is being rendered using dtcTemplate. But how is this possible if dtcTemplate is not in the DataSharing folder? Because of Acquisition, DataSharing acquires dtcTemplate from its parent (Objects) who acquires it from its parent (Outline). But because of Acquisition, dtcTemplate appears to be (and acts) like a regular member object of DataSharing.

So if that's the case, why do all of the leaves in object have a similar style but different content? The DTML source code for the dtcTemplate document is as follows: 

<!--#var standard_html_header-->
<!--#var dtContent-->
<HR>
<!--#var standard_html_footer-->

The dtContent is a DTML document inside of each subfolder that gets inserted into the dtcTemplate document. Again, each leaf appears different because the dtContent is specified at the leaf level here, while keeping a similar identity because the dtcTemplate document that is being called to render each leaf is shared across all of the leaf subfolders. When we started working on this QuickStart project, a dtContent document was defined in the top folder that is being used for the entire QuickStart tree that you are now reading so that all of the leaves would render a simple document until a real dtcTemplate was defined for their level. Meaning: all of the empty folders acquired the default document from higher up until it got overridden.

qU_varsq }q u.=)*o;/(cOFS.Document Document qNtq.}q(UtitleqUqUrawqT

Zope and Aqueduct take great pains to maintain high transaction rates and performance. Chief among these is the persistent database logins established and maintained by Aqueduct. Multiple, persistent logins (each with their own database privileges) can be created and maintained.

Another signficant performance boost also comes from the fact that Zope (and hence Aqueduct) are long-running processes. This completely avoids the performance-bashing startup latency associated with complex CGI applications.

qUglobalsq}qU__name__q U dtContentq U_varsq }q u.?)*o;/(cOFS.Image Image qNtq.}q(UsizeqM U content_typeqU image/gifqUdataq(U@q(U OFS.ImageqUPdataq tq tq QU__name__q UMultiSourceAqueductDiagram.gifq UtitleqUqu.@)*o;/(cOFS.Image Pdata qNtq.}qUdataqT GIF89a !, @I8ͻ`(dihlpmO-:=nal k_nVجv2 ;zFw|.sB:c9TIMt_G`~cX77w{w^rHq1Ea65->,Y3gyRf#)%ψt&ن0$"!]@ma H h7/x_K7(jd:)h'pp:hy+`HT'"36b1qS:TzLOZ;-k%x7Qk^Mv%FԐ Kڒ&6\ng>i™%Ø+!G \g0&x|U#Zm5UbW9`TMdu׀U ΖNguw;tbt1}gn'7;cRj_UӑRQڣd37N!M8 +a"ie !C9%]%܆NN„W0dx-D~0KeKZ^rRi0F2ϗ$/kg~"6(< >f0$V6Re6хBy3Om=Wɀ"N7bd( 6-yИ ZVЈlkD-s3 #GMx$'r?G*]ms^$6BvQLZǦ7]fozJږBڇ dL5Dvԩׇ9 (XRRsnj%#ZP*I~`T֧Jm`R URYOXkE+=:*Ge;Cˤ͏cҚe7^jOKޥT-kE:Q'\.n\pA[TގIխKY1].mv5>e>]uFxKy#C5t[{[ ͯ~pG)`r9VS|RT#<hp9Rr Y\_ʀ& E})vq+W>)NzEWN1Ij>f3‹F>:]R9 b"+ V,1*W+cx+|l4zoɾB;F>2${{-u  |2)ers%d3dWWHgʕM-xEHHYvW|dC=(d_tI]C F!ôdeZ03:}n$]Zꎱֳ5<2[˓sMPr'ŊJ}ԘsYq*!:Vi{)U^.gUEMJ`lbwl@`S7U qOֳ/owmJN'<78ڱ/xxٽK;ʚЙysx98X-3͎Ejį*q*sat,LG;9vsq]o$jJwgx&Q7>j +886E#9clYU7y0] /B=f~҆4]!_ 9;a[܉x"ȕ'+#7?ëvpN4Wqr4kنfiǻVU#;o?[:0PTvbw+|g{Ser XvutDWs(%S~9NU]tvY*pt|$g TueRAwVF-m@06e;4X1pN#rW'{N7?ăy{sҁp\h؆RĄGJ8ddvZ7WJ1uvbOiu3#__D҂1Gyf!V@7S00w!4[kh"3']ciJ1`BTw\keՕV%GHW]<~jIQ-Vɘ79)Eŗ.3((8Mhm7{x9+E՚(yɇ]ǒ16DE)}gv8^əCGK0izGy/ɍ t/wfx+f3뙚كIr(w)`yw/)ڥx1ii~YSwnAh ":$Z&JxXHdwfN) 'Rtd/~1*e+7x%D׶I4?JLڤN2;qs.>)*o;/(cOFS.Document Document qNtq.}q(UtitleqUqUrawqTB

Aqueduct can also be implemented in a multi-database architecture. What if your sales data was kept in Oracle® on sales.plutonia.com and your human resources data was kept in a Sybase® database on hr.plutonia.com. All this and your web server of choice is Apache on Linux! Sound like an impossible situation!? Not with Zope and Aqueduct. Consider the following diagram which implements this very architecture.

qUglobalsq}qU__name__q U dtContentq U_varsq }q u.A)*o;/`(cOFS.Document Document qNtq.}q(UtitleqUqUrawqT

Zope (and therefore Aqueduct) runs on many platforms. This list is always growing! The lastest list of supported platforms and databases can be found on our website.

As of April 1998, Digital Creations supported:

  • Linux v2
  • BSDI v3
  • OSF1v3
  • Solaris 2.5
  • Solaris 2.6
  • HP/UX 10.x
  • Irix 6.46
  • Windows NT Server v4
  • Windows NT Workstation v4
qUglobalsq}qU__name__q U dtContentq U_varsq }q u.C)*o;/(cOFS.Image Image qNtq.}q(UsizeqMFU content_typeqU image/gifqUdataq(UDq(U OFS.ImageqUPdataq tq tq QU__name__q UNTierAqueductDiagram.gifq UtitleqUqu.D)*o;/s(cOFS.Image Pdata qNtq.}qUdataqTFGIF89a@!,@@I8ͻ`(dihlp,t]O_GV GRL.ШtJ5F1j{Wr9ΪI_7y ֭^ ;}E]c{7~h'bo>r^B3G.p[nP@+VrDžZsv#׋eѕd㟠k(݂|ߺs*ӗl ft"$F"1Dɓ(S\Y9%͉oNu)Ҳ?{BLjh Յ+-O7$s  ULK:%Eo"W+ ̭Yd*^sfkBkˎ kܫ.g|ud+{Nk{,֓kзEo` Nwȓ+y|gFNֳks&J*=OkϿ߀\g&`<n]Vxaf!n4zUx#NA&u,r&-(# މmbw&h3؋6@)^5u_aEǖ= $difK`lPKXnֹ_zi)|aߡ&|XcMXe4唌fڑAi逤m] 9@#k(<:Rqj~XYwlIXJ*NA"&yl,:JݖD"ʒ"kymkb}/+RoX !龽*ĩIQ%Ý)$B( 镚N9 56"΅0D cHC cwf~5D,*(AZ,(ZXVE R,Ib%F XE5񍅒YE'8 .g_Ȣ(nGEBj B>INrw؛⸿ŅT^?iT@yxl)cnle1mD1DIƂ(Ddβ 2]NF?$R VLT3beT`/ujm@)qjmSӖUv2 $dn#טB^}Mz_vY+^*ivH|Bڑ>˚.I߅ZU,z7Wlc3z7ad%m@9sMϩ&awVm`Em7s 7>Hh/^n9V'Khf_[v񘳤qk`꣞ Y]q fRϛ̴YhSge^/N~[6ڠn0*aMg=j$YZ}E&[a<Watw^'?}Bh«:6'z<1= Dbg1N+iCy7ӷm|A5%2ק%X]']BOg kFi~buwSfhl˖p~u8mfb7Zy29KO.gM9.IWiS\ٕ^`bgegT#>wY7gd?#xkQwt%t;u8sJvmk^spF>ɅijISC5\bNKWcY֧}c)=py0̸y\w؎fmSuVLck'gxvIR跁ITbNrECH*9n'ԕ\Dphutq'voV$|B穆Iö%IxXSmv})$ꉚX6%h | f~DW:YGgڟBeDJ喢DnAF`!ʋ'z}B5Y m%ƜNjNG' C'bVHT٣֢aTYEhLzkPnXÅ.f"q-ƥ#vnjh2}zW3R*~(2'LXJzb87Y<)*[*?4H.o  ,cڴ*&`TY:ڱO[o- Uj\El7Z:7Rylli~&|I'm`aopCl@3{h~䴨jL}Bf?ޣ~_sWW }\v+l*_j+&@*㺴$GZ:I{\Z HĄk4*+S۽ZGT)+A߫w?4X=4D=ӿ,Iz@ YY~V{]]͒+|Q{Ln1}ýf>9}T]nK)nr2)iտ "~\੦Ȁ:@Iέqu|EG4-\~WUCdl]ObʄV>d]p(Eeؐ nyݑX撌Thu=E_<$Q#"&(OĜ6M.`AN =khϨBM~/ni}h,{^؊40-!fL!NtFY͌鼚..Mv]>ixcQXk'EW ~k^UymW"ܕrN.aNՄHJnq?~G2~K/Ǝ,.(۵n ?r7 {>xf^aq>A/F8XY̅|׌X.]M-d_fm!jȾgyGه8X, ?v_F'm2l 3%B:$OrOt$/-+s?]+ECpg?¬빯R['nɗOaE?Oĝ5'ZNҎwg/O?|t?O%1NEs3PZ9ONZYoCq$KDS5y%`~㩦u罸n/C&KfFELV¬[iwR8.Ekv}rz~ $,4;RZ~65. '+_=톏 P@!";qs.B)*o;/ (cOFS.Document Document qNtq.}q(UtitleqUqUrawqTw

Arguably the most powerful and complex implementation of Zope is one which involves a multi-tier architecture and multiple datasources.

Consider the following common scenario:

For various and sundry reasons Plutonia Computer's (our example company) webmaster has chosen to run the main Plutonia website on the Linux operating system and use Apache as the web server. Unfortunately for our webmaster, Plutonia's corporate database standards are Oracle® and Sybase®. Last we checked, neither Sybase or Oracle had (or were planning on having) client-side drivers for Linux. If they did a clever and efficient webmaster could develop interesting CGI applications against the client-side drivers. Alas, no drivers, no integration...

Until Zope and Aqueduct that is! Using Zope's unique Network Client capabilities, Zope developers can publish searchable objects from one Zope to another. In the scenario above a developer can use Zope on a platform for which there are Oracle/Sybase client drivers. From this platform they would publish one or more query objects. For example, Oracle client drivers are available for the Solaris operating system. We can use Zope on Solaris to publish (over the network) queries against an Oracle database. This Oracle database is either a) on the same Solaris machine, or b) available to the Solaris machine over the network. In any case, the following queries can be published by the Solaris server.

Searchable Object Query String
qryListAllCustomers SELECT * FROM customers
qryListAllBackOrders SELECT order_id, quantity, part_number FROM orders
WHERE shipped < quantity

We can now return to our Linux web server where we use a Network Client to access the remote searchable objects published from the Solaris server. Once we correctly configure a Network Client we have access to all of the data on Linux!!! This architecture works perfectly whether you are SELECTing, UPDATEing or INSERTing data. As a matter of fact it even works for CREATEing and DROPping your tables!

Security and Performance is critical! The network connection between the Linux web server and the Solaris machine that is publishing searchable objects is both encrypted (for strong security) and compressed (for strong network performance).

The scenario described above is illustrated in the following software component diagram. Note that while not depicted on the diagram it is certainly possible (and, in fact, common) for the Linux webserver the be publishing databases (e.g., SOLID, mySQL, mSQL, etc.) directly in conjunction with the Oracle and Sybase databases.

qUglobalsq}qU__name__q U dtContentq U_varsq }q u.F)*o;/ (cOFS.Document Document qNtq.}q(UtitleqUqUrawqTv

Here's a common problem... The people that are experienced and talented in the development of efficient SQL queries are often not the people that have the best eye for aesthetics and presentation. Similarly, an organization's best graphics specialists and HTML authors might not be qualified to write efficient SQL. What to do?!

The combination of Zope and Aqueduct allows website managers to segregate the responsibility for the SQL queries from the responsibility for developing a visually attractive and appealing interface. Consider the following SQL query (note the template variable substitution is highlighted in red:

SELECT
parts.part_id, description, price,
order_number, quantity, shipped,
customers.name, customers.address
FROM parts, orders, customers
WHERE
parts.part_id = orders.part_id
AND
orders.customer_id = customers.customer_id
AND orders.order_number = <!--#VAR order_number-->
 ORDER BY order_number

This query is certainly not the most complex or complicated query that's ever been devised. However, it does involve joining two relational tables and sorting/ordering the output. So, while not terribly complex, it might very well be beyond the expertise of an HTML developer or graphics artist. No problem! Just get your local SQL guru to create a Zope SQL Method that implements this SQL query. Let's call it qryListOrderInformation.

With the qryListOrderInformation object created our HTML developers and graphics artists can do what they do best... make the site look visually appealing. Our graphic designer can now access the data returned from the query using the Document Template Markup Language (DTML) as follows:

When the query was run, it would return data which would, in turn, be merged with the template to produce the folllwing HTML: 

<table>
  <tr>
    <th>Order<br>Number</th>
    <th>Quantity</th>
    <th>Shipped</th>
  </tr>

    <tr>
      <td>2</td>
      <td>4</td>
      <td>3</td>
    </tr>

    <tr>
      <td>3</td>
      <td>6</td>
      <td>0</td>
    </tr>

</table>

Which when rendered in a browser would appear as follows:

Order
Number		 Quantity Shipped
2 4 3
3 6 0
qUglobalsq}qU__name__q U dtContentq U_varsq }q u.E)*o;/(cOFS.Image File qNtq.}q(UsizeqMU content_typeqUapplication/octet-streamqUdataq(UGq(U OFS.ImageqUPdataq tq tq QU__name__q Usample_aqueduct_dtml_snippetq UtitleqUqu.G)*o;/K(cOFS.Image Pdata qNtq.}qUdataqT
Order
Number		 Quantity Shipped
qs.I)*o;/(cOFS.Image Image qNtq.}q(UsizeqM U content_typeqU image/gifqUdataq(UJq(U OFS.ImageqUPdataq tq tq QU__name__q USingleTierDiagram.gifq UtitleqUqu.J)*o;/ (cOFS.Image Pdata qNtq.}qUdataqT GIF89a !, @I8ͻ`(dihlp,TvO?N+| GaΞJZج3t0+.h8J%ӫ;ک^jsB2JS~(0eZn4m<<`7rE.-dmpHRCkpl"Xīf`aPTѫ'|:qtoٿ)%#Qgu站0Rw >LA%a Nc.aL8nLƓtfXhRʊj2ys|QAtGɁ%tF1o%A9f*F\ojɃ=zj#&]er +Xix漣۟bʝKnPJ m^F H7 ˷q`OLS_q̹[zMAܐ/fӰcGThP^hۮ_.MP&i/ ^NgkGG7ӫ7.}K2?ϟ*' =5&< Q6fYa\\QUqTA!l݈xkmu]㎸eO(X~B5V}M}$4\J b(3-erfRU"J(F!H fV^'ZߚXgOB3ߠX%~.$ЈZ&mTXԗQa wFWhkif^*WDS)se8} +1z k]窝=[byMŒڸkdAbܹ;iyݙbբoqJl0z*t.l>^ql\QcxLj8 c1[3<І0.H+$IMGm|RW} Vg(Zw / h594! mL9g 6MQ,tC-K^'ҍ^JW7n%Fj]J#.t]\SRj+؏26S;RF`^>&:ȧ{n^&w2_rO!E40Ӿ`b=G{Cb/"?0 RˬgzXTF(HIp ˨Fǫ:mo'zt;(L 5:EʁƊa/ !x M1oFzC;d5|R(<Au,щMt%_Ec\6B B† uҪ'" /; %2>D$#0E]aZ_Ikv$g@uKKFH:E!$2i'LVdLXӸXڒ] a.|ӵr5+JK;e"KN4W@!K v4Y4Dx,gܬ~ RIb9K+va8(vV;ZA' f.kC?T&h>*bB(HT(,OҖB.]pioQIc?ɓ˟dӢz4*O£T۔Ԡ@uH"x՘v8EYfUfuq6`YoҭzkE/WQ.ϩq(;zbj^fקg}W0A b/6UFeьf h5-gZ jcBdqvE oKwaaqM α\tKZ]. kZBpSϡ^S-R`1ֹvcܐ(MX6O Tbf10bawøV5["ʆJ"̂H|:_ՊިiX 466Fȉ7㴱v"[*Cdi.̞/޶U<]L:mAM8w<o;Yq*d̴ rIN1H>/Ѡ&3LtvNjf EH Z4-6ш3UƜ$bt(HnRXϡdg4B'=@5ci-KGF5ݻۜu۬l!L/8)KmRK *-}HPkۉ4HCB[Cs$siH2WkD!H78!^&^I x?䖷ı3Y.qo1 akfGHw (7ZÓcʇ^;zyxO{a'.3S:ߜusnBҕLϤ\_'NŸ(٣DG˝7}('뜳סy^#@clMP::qq)\ v e54$&C٧ouvDXln/ZZvqruӾr0ۨ _#{6l/MgK>9D T4&}vzQb_ W8aB% |%ThevjgthEY6Z#Xg{What's the secret?

It's no longer a secret... The fastest way to show significant demonstrable returns from your internet/intranet/extranet website is to web-enable existing operational databases. A close second is the design and development of new web-centric databases designed to deliver enhanced sales, marketing and customer service capabilities to your organization. Like we said, what needs to be done is no longer a secret.

How to do it...

Today's most precious commodity? Your time. In Zope (our web application development and delivery platform) and Aqueduct (our relational database publishing solution) Digital Creations has developed a suite of software that lets you work smarter, not harder.

Take for example, Aqueduct. Aqueduct packages your database queries (i.e., the SQL queries) into reusable objects that are made available throughout your website in accordance with the security parameters you establish. Aqueduct supports two-tier and n-tier implementations. Consider the following diagram which depicts a single-tier Aqueduct implementation. This diagram might depict a centralized web server serving data from a centralized database server.

Key Description
1
 "Standard" web-browser (whatever that means!)
2
 A "Standard" web server: (e.g., Apache, Netscape's Enterprise Server, Open Market's web server and others). Zope's long running process is messaged by very small CGI programs launched by the web server. This elegant architecture allows Zope to easily scale into higher transaction rates.
3
 Zope Server Process: Zope is based on a strong web-to-objects model that marries an object-oriented database and scripting envrironment with user sessions, an Undo capability and more. It is the well-matched interface between this object-orientation and underlying relational databases that is Aqueduct's most distringuishing feature.
4
 Aqueduct SQL Method(s): SQL Methods expose templated SQL statements to the Zope object system. This exposure allows you to take advantage of Zope capabilities like Acquisition, hierarchical security and authentication, Folder Properties and Document Template Markup Language.
5
 Aqueduct Database Adapter: On Unix-variant operating systems Aqueduct uses native database libraries and persistent database connections for high-performance database operations. On Linux Database Adpaters are available for mySQL, miniSQL, and SOLID. However, the list of supported databases is growing all the time. Please check our website for the most current list.
6
 A "Standard" Database Server: Examples include SOLID, mySQL, mSQL and others.
qUglobalsq}qU__name__q U dtContentq U_varsq }q u.K)*o;/(cOFS.Document Document qNtq.}q(U__name__qU dtContentqUglobalsq}qUrawqTZConsider the following basic personnel report. This report highlights (in red) anyone whose last raise was more than 25%.

Personnel Report

Plutonia Company - Marketing Department peronnel listing as of 1/1/98:

Employee Number Name Department Email Current Salary Last Raise (%)
SJ34 Jones, Steve Marketing stevej@plutonia.com [SEND]
$50,995
27%
JD334 Doe, James Marketing doej@plutonia.com [SEND]
$43,995
24%

Example Code - The SQLMethod

This is implemented with two basic objects. The first object is the SQL Method (which we've named qryAllMarketingEmployees as follows:

SELECT * from PlutoniaEmployees WHERE
department = '<!--#var department-->'

You should note that this SQL statement is actually an SQL statement template. The variable department will be inserted into the SQL statement when the query is run. In the example above the variable department is equal to MARKETING. Thus, when this SQL template is rendered the following SQL statement is sent to the database for evaluation/execution:

SELECT * from PlutoniaEmployees WHERE
department = 'MARKETING'

An SQL Method returns a sequence of items which can be interated over inside other queries or in HTML document templates. In this particular example, this query returns the following results:

employee_id last_name first_name department emailaddress salary precent_raise
SJ34 Jones Steve Marketing stevej@plutonia.com 50995 27
JD334 Doe James Marketing doej@plutonia.com 43995 24

Example Code - The Document Template

The second object is the Document Template required to render the HTML page. The table above was created with the following DTML:

<!--#var standard_html_header-->
<h3>Personnel Report</h3>
<p>
Plutonia Company - Marketing Department peronnel listing as of 1/1/98:
</p>

<table border="1">
  <tr>
    <th>Employee Number</th>
    <th>Name</th>
    <th>Department</th>
    <th colspan="2">Email</th>
    <th>Current Salary</th>
    <th>Last Raise (%)</th>
  </tr>

<--#in qryAllMarketingEmployees-->

  <tr>
    <td><!--#var employee_id--></td>
    <td><!--#var last_name--></td>
    <td><!--#var department--></td>
    <td><!--#var emailaddress--></td>
    <td><a href="mailto:<!--#var emailaddress-->">[SEND]</a></td>
    <td><center>$<!--#var salary-->;</center></td>
    <td>
      <!--#if expr="percent_raise > 25"-->
        <font color="FF0000">
        <!--#var percent_raise-->%
      </font>
      <!--#else-->
        <!--#var percent_raise-->%
      <!--#/if-->
    </td>
  </tr>
<--#/in-->
</table>

Take note of the <!--#in QUERY_NAME--> tag which allows you to loop through a section of document template once for each "record" or item in the sequence. Also note that the percent_raise value was highlighted in red (using the HTML <FONT> tag). This was done using the Document Template expr tag which allows us to evaluate arbitrary expressions. In this case, if percent_raise is less than 25 no highlighting is done. If, however, the percent_raise is greater than 25 the value highlighted.

These are only a few of the powerful capabilities in Aqueduct! If this looks interesting, read on!

qU_varsq }q u.)*o;/(cOFS.Document Document qNtq.}q(UrawqU2

This is a document about

qUglobalsq}qU__name__qU dtContentqU_varsq }q u.O)*o;/F(cOFS.Document Document qNtq.}q(UtitleqUqUrawqT

Zope automatically provides useful objects for web site builders. These include Documents, Images, Folders, UserFolders, and MailHost objects. A content manager can use these objects to create a highly interactive, yet maintainable web site. Content managers can take advantage of Zope's powerful object model and data sharing abilities to reduce redundant work and delegate responsibility for content.

Most web sites try to maintain a consistent style, such as common HTML menus or feedback links. Using Zope, a content manager can define a Document that renders the HTML menu in one Folder - and simply refer to that from other Documents in the system. When the menu needs to be changed, it can be changed once and the changes will instantly be visible throughout the site.

Documents also give content managers access to HTTP request variables, cookies, programmatic control of the object system and more. A content manager could create a Document that renders itself completely differently based on the browser, identity or even the remote network address of the viewer. Using the built-in Zope MailHost object, one could even arrange for a Document to send out an email anytime it is viewed!

qUglobalsq}qU__name__q U dtContentq U_varsq }q u.P)*o;/4(cOFS.Document Document qNtq.}q(UtitleqUqUrawqT

Drop-in products for Zope provide allow content managers to add new functionality like discussion groups and database access to their site as easily as they new add Documents or Folders. Products designed for Zope register new types of objects which can be dropped into any Folder - even into objects defined by other products!

The Confera product adds the ability to create full-featured web discussion groups to a site. A content manager can simply add a new Confera Topic in any Folder. The newly added Confera Topic is fully functional, complete with generic Documents that can be customized to brand the topic and full-text searching.

The Aqueduct line of products allow content managers to easily integrate back-end data with their site by dropping in Database Connections and Database Methods which perform database queries. The resulting data can then be used in site Documents, taking full advantage of DTML.

qUglobalsq}qU__name__q U dtContentq U_varsq }q u.Q)*o;/(cOFS.Document Document qNtq.}q(UtitleqUqUrawqT

Zope Documents provide a powerful system for dynamic content delivery. Documents add rich programming to HTML, including iterations, conditional testing, variable insertion, access to HTTP headers, cookies, and more. Since these rich HTML templates are objects, your users can undo mistakes, work on Documents in private Sessions, and take advantage of Zope's built-in security. These rich programming additions are known as the Document Template Markup Language (DTML), a server-side-include style syntax.

qUglobalsq}qU__name__q U dtContentq U_varsq }q u.)*o;/(cOFS.Image Image qNtq.}q(UsizeqKU content_typeqU image/gifqUdataq(URq(U OFS.ImageqUPdataq tq tq QU__name__q UClosedBook.gifq UtitleqUqu.R)*o;/(cOFS.Image Pdata qNtq.}qUdataqUGIF89a!,@D0~Q}6^F'zm+&LB9"&& qtAhjG%e;qs.)*o;/(cOFS.Image Image qNtq.}q(UsizeqKU content_typeqU image/gifqUdataq(USq(U OFS.ImageqUPdataq tq tq QU__name__q U OpenBook.gifq UtitleqUqu.S)*o;/(cOFS.Image Pdata qNtq.}qUdataqUGIF89a!,@RY¤aT )`r<gDTPBW'+9#h%`[60R dJVAt:xߋ;qs.)*o;/(cOFS.Document Document qNtq.}q(UtitleqUqUrawqT Zope QuickStart

Welcome to Zope - a new generation of software that we call a web application platform. Like web application servers, Zope provides very high performance and a strong framework for dynamic applications.

This QuickStart is built with Zope objects -- take a look!

Zope, though, is distinguished by its integrated object database which, when combined with a revolutionary object model, provides a completely unique facility for servicing content managers and web application developers. This outline, implemented in Zope, talks about the various strengths of the Zope platform and some of the other products available for it.

Start working in the management screens

qUglobalsq}qU__name__q U index_htmlq U_varsq }q u.)*o;/ (cOFS.Document Document qNtq.}q(UrawqT<!--#var title_or_id--> qUglobalsq}qU__name__qUstandard_html_headerqU_varsq }q u.+޳p+޳*(cZODB.conversionhack hack qNtq.}qU _containerq}q(U _pack_timeqGA˗bVœU Applicationq(Uq(UOFS.ApplicationqU Applicationq tq tq Qus.9s<?p9s< ((UOFS.DTMLMethodqU DTMLMethodqtqNt.}q(UtitleqUStandard Html HeaderqUrawqUP<dtml-var title_or_id>qUglobalsq }q U__name__q Ustandard_html_headerq U_varsq }qu.9s< ((UOFS.DTMLMethodqU DTMLMethodqtqNt.}q(UtitleqUStandard Html FooterqUrawqU5

qUglobalsq }q U__name__q Ustandard_html_footerq U_varsq }qu.T9s< ((UOFS.DTMLMethodqU DTMLMethodqtqNt.}q(UtitleqUUrawqU\ qUglobalsq}q U__name__q U index_htmlq U_varsq }q u.9s< ((UOFS.DTMLMethodqU DTMLMethodqtqNt.}q(UtitleqUStandard Error MessageqUrawqTU
Zope

Zope Error

Zope has encountered an error while publishing this resource.

Error Type:
Error Value:

Troubleshooting Suggestions

  • This resource may be trying to reference a nonexistent object or variable .
    •
  • The URL may be incorrect.
  • The parameters passed to this resource may be incorrect.
  • A resource that this resource relies on may be encountering an error.

For more detailed information about the error, please refer to the HTML source for this page.

If the error persists please contact the site maintainer. Thank you for your patience.

Here, events like logging and other actions may also be performed, such as sending mail automatically to the administrator. qUglobalsq }q U__name__q Ustandard_error_messageq U_varsq }qu.9s< ((UOFS.ApplicationqU ApplicationqtqNt.}q(Ustandard_html_headerq(Uq(UOFS.DTMLMethodqU DTMLMethodqttQU__allow_groups__q (Uq (UAccessControl.Userq U UserFolderq ttQU_objectsq (}q(U meta_typeqU User FolderqUidqU acl_usersqu}q(hU Control PanelqhU Control_Panelqu}q(hU DTML Methodqhhu}q(hhhUstandard_html_footerqu}q(hhhUstandard_error_messagequ}q(hUFolderqhU QuickStartqu}q(hhhU index_htmlq utU index_htmlq!(UTq"(hU DTMLMethodq#ttQh(Uq$(hU DTMLMethodq%ttQh(Uq&(UApp.ApplicationManagerq'UApplicationManagerq(ttQh(Uq)(hU DTMLMethodq*ttQh(Uq+(U OFS.Folderq,UFolderq-ttQh(h (h U UserFolderq.ttQU_product_meta_typesq/)u.9s< G((UApp.ApplicationManagerqUApplicationManagerqtqNt.}q(U_objectsq(}q(U meta_typeqUDatabase ManagementqUidq UDatabaseq u}q (hUVersion Managementq h UVersionsq u}q(hUProduct Managementqh UProductsqu}q(hUDebug Informationqh U DebugInfoqutqUProductsq(Uq(U App.ProductqU ProductFolderqttQu.9s< ((U App.ProductqU ProductFolderqtqNt.}q(U ZSQLMethodsq(U q(hUProductqttQU ZGadflyDAq(U q (hUProductq ttQU_objectsq (}q (U meta_typeq UProductqUidqUExternalMethodqu}q(h hhUOFSPqu}q(h hhU ZGadflyDAqu}q(h hhU ZSQLMethodsqu}q(U meta_typeqUProductqUidqU MIMEToolsqu}q(hhhUMailHostqutUExternalMethodq(U q(hUProductq ttQUMailHostq!(UVq"(hUProductq#ttQUOFSPq$(Uq%(hUProductq&ttQU MIMEToolsq'(UUq((hUProductq)ttQu. 9s< ((U App.ProductqUProductqtqNt.}q(UiconqUp_/InstalledProduct_iconqUidqUExternalMethodqUmanage_distributionq NUmanage_optionsq (}q (Ulabelq UContentsq UtargetqU manage_mainqUactionqhu}q(h U PropertiesqhhhUmanage_propertiesFormqu}q(h USecurityqhhhU manage_accessqu}q(h UUndoqhhhUmanage_UndoFormqu}q(h UFindqhhhUmanage_findFramequtU_objectsq)UversionqUUtitleqU Installed product ExternalMethodq U _distributionq!NUthisIsAnInstalledProductq"Ku.9s< ((U App.ProductqUProductqtqNt.}q(UiconqUp_/InstalledProduct_iconqUidqUOFSPqUmanage_distributionq NUmanage_optionsq (}q (Ulabelq UContentsq UtargetqU manage_mainqUactionqhu}q(h U PropertiesqhhhUmanage_propertiesFormqu}q(h USecurityqhhhU manage_accessqu}q(h UUndoqhhhUmanage_UndoFormqu}q(h UFindqhhhUmanage_findFramequtU_objectsq)UversionqUUtitleqUInstalled product OFSPq U _distributionq!NUthisIsAnInstalledProductq"Ku. 9s< ((U App.ProductqUProductqtqNt.}q(UiconqUp_/InstalledProduct_iconqUidqU ZGadflyDAqUmanage_distributionq NUmanage_optionsq (}q (Ulabelq UContentsq UtargetqU manage_mainqUactionqhu}q(h U PropertiesqhhhUmanage_propertiesFormqu}q(h USecurityqhhhU manage_accessqu}q(h UUndoqhhhUmanage_UndoFormqu}q(h UFindqhhhUmanage_findFramequtU_objectsq)UversionqUUtitleqUInstalled product ZGadflyDAq U _distributionq!NUthisIsAnInstalledProductq"Ku. 9s< ((U App.ProductqUProductqtqNt.}q(UiconqUp_/InstalledProduct_iconqUidqU ZSQLMethodsqUmanage_distributionq NUmanage_optionsq (}q (Ulabelq UContentsq UtargetqU manage_mainqUactionqhu}q(h U PropertiesqhhhUmanage_propertiesFormqu}q(h USecurityqhhhU manage_accessqu}q(h UUndoqhhhUmanage_UndoFormqu}q(h UFindqhhhUmanage_findFramequtU_objectsq)UversionqUUtitleqUInstalled product ZSQLMethodsq U _distributionq!NUthisIsAnInstalledProductq"Ku.U9s< (((U App.ProductqUProductqtqNt.}q(UiconqUp_/InstalledProduct_iconqUidqU MIMEToolsqUmanage_distributionq NUmanage_optionsq (}q (Ulabelq UContentsq UactionqU manage_mainqu}q(h U PropertiesqhUmanage_propertiesFormqu}q(h U Import/ExportqhUmanage_importExportFormqu}q(h USecurityqhU manage_accessqu}q(h UUndoqhUmanage_UndoFormqu}q(h UFindqhUmanage_findFramequ}q(h UREADMEq hU manage_readmeq!utU_objectsq")Uversionq#UUtitleq$UInstalled product MIMEToolsq%U _distributionq&NUthisIsAnInstalledProductq'Ku.V9s< G((U App.ProductqUProductqtqNt.}q(UiconqUp_/InstalledProduct_iconqUidqUMailHostqUmanage_distributionq NUmanage_optionsq (}q (Ulabelq UContentsq UactionqU manage_mainqu}q(h U PropertiesqhUmanage_propertiesFormqu}q(h U Import/ExportqhUmanage_importExportFormqu}q(h USecurityqhU manage_accessqu}q(h UUndoqhUmanage_UndoFormqu}q(h UFindqhUmanage_findFramequ}q(h UREADMEq hU manage_readmeq!utU_objectsq")Uversionq#UMailHost-1-1-0q$Utitleq%U+Installed product MailHost (MailHost-1-1-0)q&U _distributionq'NUthisIsAnInstalledProductq(Ku.9s< ((U OFS.FolderqUFolderqtqNt.}q(Ustandard_html_headerq(Uq(UOFS.DTMLMethodqU DTMLMethodqttQU index_htmlq (Uq (hU DTMLMethodq ttQUidq U QuickStartq U_objectsq(}q(U meta_typeqU DTML MethodqUidqh u}q(hUFolderqhUOutlinequ}q(U meta_typeqhUidqhu}q(hhhUstandard_html_footerqutUtitleqUZope QuickStart Outlineqh(Uq(hUFolderqttQh(Uq(hU DTMLMethodq ttQu.9s< s((U OFS.FolderqUFolderqtqNt.}q(UidqUOutlineqU_objectsq(}q(U meta_typeq UImageq Uidq UClosedBook.gifq u}q (h h h U OpenBook.gifqu}q(h UFolderqh UDatabasequ}q(h hh UContentqu}q(h U DTML Methodqh U dtcTemplatequ}q(h hh U dtContentqu}q(U meta_typeqUFolderqUidqU Applicationsqu}q(hhhUObjectsquth(Uq (UOFS.DTMLMethodq!U DTMLMethodq"ttQh(Uq#(U OFS.Imageq$UImageq%ttQh(Uq&(hUFolderq'ttQh(Uq((hUFolderq)ttQh(Uq*(hUFolderq+ttQh (Uq,(h$UImageq-ttQh(Uq.(hUFolderq/ttQh(Uq0(h!U DTMLMethodq1ttQUtitleq2Uu.9s< ((U OFS.FolderqUFolderqtqNt.}q(UPublishq(U7q(hUFolderqttQUidqUDatabaseq U MultiPlatformq (U:q (hUFolderq ttQU MultiRoleq (U8q(hUFolderqttQU_objectsq(}q(U meta_typeqUFolderqUidqU BasicExamplequ}q(hhhUHighPerformancequ}q(hhhh u}q(hhhh u}q(hhhU MultiTieredqu}q(hhhU MultiSourcequ}q(hhhhutUtitleqUDatabase Integrationq h(Uq(UOFS.DTMLMethodq U DTMLMethodq ttQUidq U MultiSourceq U_objectsq (}q(U meta_typeqU DTML MethodqUidqhu}q(hUImageqhUMultiSourceAqueductDiagram.gifquth(U?q(U OFS.ImageqUImageqttQu.79s< ((U OFS.FolderqUFolderqtqNt.}q(UtitleqUPublish DatabasesqU dtContentq(UHq(UOFS.DTMLMethodq U DTMLMethodq ttQUidq UPublishq USingleTierDiagram.gifq (UIq(U OFS.ImageqUImageqttQU_objectsq(}q(U meta_typeqU DTML MethodqUidqhu}q(hUImageqhh utu.9s< ((U OFS.FolderqUFolderqtqNt.}q(UidqUContentqU_objectsq(}q(U meta_typeq UFolderq Uidq UBuiltinq u}q (h h h U Documentsqu}q(h h h UDropinqutUtitleqUContent Managementqh(UMq(hUFolderqttQh(ULq(hUFolderqttQh (UNq(hUFolderqttQu.N9s< ((U OFS.FolderqUFolderqtqNt.}q(UtitleqUBuiltin ObjectsqU dtContentq(UOq(UOFS.DTMLMethodq U DTMLMethodq ttQUidq UBuiltinq U_objectsq (}q(U meta_typeqU DTML MethodqUidqhutu.L9s< ((U OFS.FolderqUFolderqtqNt.}q(UtitleqUDocument TemplatesqU dtContentq(UQq(UOFS.DTMLMethodq U DTMLMethodq ttQUidq U Documentsq U_objectsq (}q(U meta_typeqU DTML MethodqUidqhutu.M9s< ((U OFS.FolderqUFolderqtqNt.}q(UtitleqUDropin ObjectsqU dtContentq(UPq(UOFS.DTMLMethodq U DTMLMethodq ttQUidq UDropinq U_objectsq (}q(U meta_typeqU DTML MethodqUidqhutu.9s< ((U OFS.FolderqUFolderqtqNt.}q(U Scriptingq(Uq(hUFolderqttQUidqU Applicationsq U_objectsq (}q (U meta_typeq UFolderq Uidqhu}q(h h hUExternalqu}q(h h hUTabulaqu}q(h h hU Smartdataqu}q(h h hULeverquth(U q(hUFolderqttQUtitleqUApplication Developmentqh(Uq(hUFolderqttQh(Uq(hUFolderqttQh(Uq(hUFolderq ttQu.9s< ((U OFS.FolderqUFolderqtqNt.}q(UtitleqUDTML ScriptingqU dtContentq(U%q(UOFS.DTMLMethodq U DTMLMethodq ttQUidq U Scriptingq U_objectsq (}q(U meta_typeqU DTML MethodqUidqhutu.9s< ((U OFS.FolderqUFolderqtqNt.}q(UtitleqUExternal MethodsqU dtContentq(U#q(UOFS.DTMLMethodq U DTMLMethodq ttQUidq UExternalq U_objectsq (}q(U meta_typeqU DTML MethodqUidqhutu.9s< ((U OFS.FolderqUFolderqtqNt.}q(UtitleqUProgramming Data with TabulaqU dtContentq(U"q(UOFS.DTMLMethodq U DTMLMethodq ttQUidq UTabulaq U_objectsq (}q(U meta_typeqU DTML MethodqUidqhutu.9s< ((U OFS.FolderqUFolderqtqNt.}q(UtitleqU)Adding Object Behavior to Relational DataqU dtContentq(U$q(UOFS.DTMLMethodq U DTMLMethodq ttQUidq U Smartdataq U_objectsq (}q(U meta_typeqU DTML MethodqUidqhutu. 9s< ((U OFS.FolderqUFolderqtqNt.}q(UtitleqUThe Almighty LeverqU dtContentq(U!q(UOFS.DTMLMethodq U DTMLMethodq ttQUidq ULeverq U_objectsq (}q(U meta_typeqU DTML MethodqUidqhutu.9s< ((U OFS.FolderqUFolderqtqNt.}q(U Integratedq(U)q(hUFolderqttQUUndoq(U+q (hUFolderq ttQUidq UObjectsq U_objectsq (}q(U meta_typeqUFolderqUidqhu}q(hhhU DataSharingqu}q(hhhU Managementqu}q(hhhUNiceURLsqu}q(hhhUSecurityqu}q(hhhUSessionsqu}q(hhhhuth(U'q(hUFolderqttQh(U(q(hUFolderq ttQh(U&q!(hUFolderq"ttQUtitleq#UWeb to Objectsq$h(U*q%(hUFolderq&ttQh(U,q'(hUFolderq(ttQu.)9s< ((U OFS.FolderqUFolderqtqNt.}q(UtitleqUIntegrated Object DatabaseqU dtContentq(U0q(UOFS.DTMLMethodq U DTMLMethodq ttQUidq U Integratedq U_objectsq (}q(U meta_typeqU DTML MethodqUidqhutu.&9s< ((U OFS.FolderqUFolderqtqNt.}q(UtitleqU Data SharingqU dtContentq(U3q(UOFS.DTMLMethodq U DTMLMethodq ttQUidq U DataSharingq Udatasharing1.gifq (U4q(U OFS.ImageqUImageqttQU_objectsq(}q(U meta_typeqU DTML MethodqUidqhu}q(hUImageqhh utu.*9s< ((U OFS.FolderqUFolderqtqNt.}q(UtitleqUManaged Through the WebqU dtContentq(U/q(UOFS.DTMLMethodq U DTMLMethodq ttQUidq U Managementq U_objectsq (}q(U meta_typeqU DTML MethodqUidqhutu.(9s< ((U OFS.FolderqUFolderqtqNt.}q(UtitleqUDirect URL Access to ObjectsqU dtContentq(U1q(UOFS.DTMLMethodq U DTMLMethodq ttQUidq UNiceURLsq U_objectsq (}q(U meta_typeqU DTML MethodqUidqhutu.'9s< ((U OFS.FolderqUFolderqtqNt.}q(UtitleqUSecurityqU dtContentq(U2q(UOFS.DTMLMethodq U DTMLMethodq ttQUidq USecurityq U_objectsq (}q(U meta_typeqU DTML MethodqUidqhutu.,9s< ((U OFS.FolderqUFolderqtqNt.}q(UtitleqUSessionsqU dtContentq(U-q(UOFS.DTMLMethodq U DTMLMethodq ttQUidq USessionsq U_objectsq (}q(U meta_typeqU DTML MethodqUidqhutu.+9s< ((U OFS.FolderqUFolderqtqNt.}q(UtitleqUUndoqU dtContentq(U.q(UOFS.DTMLMethodq U DTMLMethodq ttQUidq UUndoq U_objectsq (}q(U meta_typeqU DTML MethodqUidqhutu.?