No, it doesn't. The cache system CUTS DOWN on processor use by storing frequently requested pages.
That is not Infopop's concern.
Such as?
Uh, no. Tell me, do you know what the cache system does, exactly? If you knew, you'd find that it has virtually nothing in common with client side caches.
No, they don't.
No, they don't.
That confirms it for me - you have no idea how to program in Perl. It takes almost no time at all for the system to open and compile the required file, which contains all of ONE hash with the needed wordlet package.
The only thing in your rant that I might agree with.
What would be the use of that?
So, let's go over the caching system one more time, mmm'kay?
1) User calls a page
2) UBB checks to see if the page is cached
3) Let's say this is a thread. Let's also say that the thread is not cached
4) The UBB opens the thread datafile. For each post in the thread, it opens the required user profile, caches that data, then builds the post using the templates. This is an expensive process
5) After the page has been built, it's cached and then passed to the user
6) Another user comes along
7) Because the page is cached, it is fed back to the user with no further processing required
The same thing applies for thread listings.
1) User calls a page - this time it's a thread listing (forumdisplay)
2) UBB checks the cache
3) UBB finds it's NOT cached
4) UBB builds the thread listing - in order to do so, it needs to read EVERY THREAD. This is an expensive process
5) UBB caches the thread listing and passes it back to the user
6) Another user comes along
7) Because the page is cached, it is fed back to the user with no further processing required
This helps a TREMENDOUS ammount to reduce required processor time.
Please, before posting rants, learn all you can about the topic. Shooting your mouth off tends not to leave people with a very good impression about you.
[ February 20, 2001: Message edited by: Charles Capps ]
