[Zope-dev] Fw: [Zope-dev] wygiwys

[Martijn Faassen]

Damian Morton wrote:

[snip]

> In fact, the a website as a whole could be viewed as a DOM structure, and
> there are many advantages to this. For example, if we assumed that our
> programs elemenst were functional DOM consumers and producers, you could
> eliminate much of the dynamic nature of a website. In my experince, there is
> a whole lot of stuff about a website that only changes slowly - it doesnt
> need to be re-created for every page view, only when the source data
> changes. If you could decompose a website into a kind of feedforward
> dataflow machine and add some intelligent caching, you would have a very
> efficient dynamic website.

I'm not sure I really get this. I know caching would be useful, but I don't
see how the DOM nature of a website helps here.

> What would be needed for that would be for the
> programmed part of the website to conform to functional or dataflow
> programming - each module or function would take objects as input and would
> create or modify existsing objects. Might mesh well with the ZODB mechanism.

Actually, the Zope database is already exposed as an (XML) DOM tree in Zope
2. Look at ZDOM.py in lib/python/OFS. That's also how Zope 2 does XML export.

I haven't seen much other leveraging of the DOM-ness of the Zope database
yet, though. Any ideas?

Regards,

Martijn