vBET 3.3.4 released

[Snake]

I dont understand this file cache, why would you need a 2nd cache, the main one already caches pages and only updates when new content is added, so why cache it for 1 hour again, your explanation is difficult to understand.

[vBET]

I dont understand this file cache, why would you need a 2nd cache, the main one already caches pages and only updates when new content is added, so why cache it for 1 hour again, your explanation is difficult to understand.

Database cache caches only translations. Not whole HTML content. So when some translated page is generated, then first normal page is generated and after that it is parsed and translated. During translation DB cache is used and translated sentences are taken from there. Just sentences - not whole HTML, because each time translations can be different (i.e. different privileges of users, changed content). One HTML page can have hundreds of sentences to translate - vBET takes content between HTML tags. Thanks DB cache those translations don't have to be taken each time from Google - what consumes lot of time - instead of that, those are taken from your local DB. Still - normal page have to be generated and after that translated.

Full File Cache For Guests works only for guests. Thanks that we do not have to worry that users have different privileges and see different things. ll guests see the same content. Because of that we do not have to parse result and translate it piece by piece each time - we can simply do it one a while and cache full HTML output. So in this case when full page is not cached, or cached content is too old, then normal translation occurs - just like described before. But this time at the very end full HTML output is written to file. So next time when same request comes from guest we do not generate even normal page content - we simply stream to guest already cached HTML file. That is why we save lot of SQL queries, CPU and memory. We just give to user content from static file. That is why it is important to determine how long this cache will be valid. Because if something will change - i.e. new post will arrive to thread, then guests will not see this new post until already cached file expires. After that during next request, again normal page will be generated, translated, and cached - and this content guests will see i.e. for another hour (configurable). They will not see any changes until cached file expires again. Of course your users will see everything, because it works only for guests (so for robots also, because robots crawl your forum as guests).

Please tell did it help and in case of any questions just ask - we will gladly describe it more