I cannot agree and let me explain.
the site is a community site. it allows keep-me-logged feature. So most 
users ( 40,000 at the moment ) are constantly logged on users.
now...
the only personalization on most pages is the user's name, the rest of page 
content is the same.
all pages are comprised of plugins that are cache-enabled. The plugin that 
renders current user name is not cache-enabled.
So pre-caching should cache all plugins for all users, it is the username 
plugin only which will be not-cached.
all visitors ( including logged on users ) should be getting content from 
the same cache and only the username plugin will be not-cached.
am I missing something?


"Steffen Kamper" <[EMAIL PROTECTED]> wrote in message 
news:[EMAIL PROTECTED]
>
> "Vahan Amirbekyan" <[EMAIL PROTECTED]> schrieb im Newsbeitrag 
> news:[EMAIL PROTECTED]
>> folks,
>> My understanding is that it is possible to pre-cache a site with a 
>> crawler .
>> Problem that I am having is related to the cache logic.
>> When a crawler hits a site no logged-on user session is created and hence 
>> all caches created will work for not-logged on users only. Since typo3 
>> cache creates separate caches for logged and not-logged on users the 
>> crawler does not seem as a semi-solution.
>> Is it possible to disable that feature in caching so that the same cache 
>> entries be used for logged and not-logged on users?
>>
>> thank you
>> Vahan
>
> it does not make sense to crawl a logged-in page, the results are 
> worthless.
>
> vg  Steffen
> 
_______________________________________________
TYPO3-english mailing list
[email protected]
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english

Reply via email to