AW: Fragmented Caching with AJAX

Hello again,
sorry, obviously I misunderstood your last question 
http://tech.groups.yahoo.com/group/zms-developers/message/3125

[a]
The "dynamic bodytext cache" option means not ajax based transfer of the
text core (of course, this is technically possible, too) but still using
zope/dtml based generation of the text core via the bodyContent_Float
template (and caching only the performance consuming navigation around). 
[b]
So there is no problem with non-AJAX or non-javascript browsers.
[c]
The new cachemanager generates dtml _documents_ (which are delivered faster
than dtml _methods_) und only the _preview_ (depending on the url parameter)
is not cached. Otherwise docs are generated and  delivered as cached to
authenticated users, too.

--------------------------------------------------
http://bscw.hoffmannliebenberg.de/pub/bscw.cgi/d300641/zms-2.11.0.tar.gz
2008-04-28::zms-2.11.0-09_2
-- MINOR CHANGES
[01035] Revoked semantics of ZMSObject.getTitle() and
ZMSObject.getTitlealt() [01033] 
--------------------------------------------------

So, I recommend publishing personalized content generated by templates
delivering via AJAX or placing them within the float area and using the
dynamic body option.

Hopefully these hints will help you
Best regards
fh, moderator

 

-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[email protected]]
Im Auftrag von Peter Zechmeister
Gesendet: Montag, 28. April 2008 10:01
An: ZMS-Developers
Betreff: [zms-developers] Fragmented Caching with AJAX

Dear Mr. Hoffmann & ZMS-Devellopers,

according to your last reply:

>[2]
>The appended screenshot will illustrate the feature's configuration:
>In spite of activated ZMS Cache the content body may be delivered
>dynamically.

A)
I tried, but I did not find AJAX requests for post-loading content. What
did I wrong ;-) ?
Is this intended as a ZMS internal feature or has the template to
support this?
If it has to be the template, which of the ZMS default templates does
support this feature?

B)
Does this feature take care of non-AJAX or non-javascript able browsers
as many of the textonly browsers are which are often used by visually
impaired people?

C) 
Does this feature distinguish between anonymous requests, where a page
can generally be cached in most cases and authentified requests, where
most often the menu is personalised but the content can get cached?

Regards
PeterZ