[IDEA] Changes to TV handling

I want to make a change to the way TVs are handled, specifically ones that query the DB but the change I make could be effective on all @Bindings.

In order to lessen the number of queries to the database using @SELECT, I am curious if anyone would be interested in having the TV output of @Bindings cached, so that TVs with the same name wouldn’t have to query the database (or file, or eval) everytime.

I have a solution in mind and would be happy to do it myself, but before I commit it to the 095dev branch I want to know from other developers if this is a good idea or not.

SOLUTION: Cache TV Commands to speed up processing,
FILES AFFECTED: manager/includes/tmplvars.commands.inc.php (ProcessTVCommand Function)

Let me know what you think.

Quote from: sirlancelot at Feb 08, 2007, 12:28 PM

I want to make a change to the way TVs are handled, specifically ones that query the DB but the change I make could be effective on all @Bindings.

In order to lessen the number of queries to the database using @SELECT, I am curious if anyone would be interested in having the TV output of @Bindings cached, so that TVs with the same name wouldn’t have to query the database (or file, or eval) everytime.

I have a solution in mind and would be happy to do it myself, but before I commit it to the 095dev branch I want to know from other developers if this is a good idea or not.

SOLUTION: Cache TV Commands to speed up processing,
FILES AFFECTED: manager/includes/tmplvars.commands.inc.php (ProcessTVCommand Function)

Let me know what you think.

It’s a good idea, but, my main concern is that this kind of caching capability would be redundant with already exists in the 0.9.7 branch. Namely, all tags can now be called cached or uncached, (i.e. [[!uncachedSnippet]], [[!*uncachedTV]], etc.), and, all database result sets executed via xPDO can optionally be cached, with various options for cache expiration and update.

Quote from: OpenGeek at Feb 08, 2007, 12:51 PM

It’s a good idea, but, my main concern is that this kind of caching capability would be redundant with already exists in the 0.9.7 branch.

Hey why re-invent the wheel

Thanks for the heads-up, I’ll wait for 0.9.7

Grab a copy from svn and start messing with it

Quote from: doze at Feb 08, 2007, 03:22 PM

Grab a copy from svn and start messing with it

Where’s the 0.9.7 branch? Looking at the code, I would guess that it’s the jason-dev branch, but if there’s a more stable or better one, let me know and I’ll test it out

Its tattoo/branches/opengeek/trunk/ and it’s updated quite often, but that’s the fun of it

Dang... Time to install PHP5....

Why is that? xPDO/0.9.7 should work with PHP 4.3.3+ -- and if it doesn’t, I guess I’ll be needin’ to fix it...

Indeed, my sottwell.com site is running on rev 2218 (I know, I need to upgrade that...) with PHP 4.4.4

Hmmm... I’ll post an error report then, as is my role