Howard - thanks for your reply.
> From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 18, 2008 3:14 PM
> Obviously, we can't predict every possible use case ahead of time.
Very true. It's notable that we have built a whole lot of functionality
on T5 without encountering any
On Jan 18, 2008 6:20 PM, Daniel Jue <[EMAIL PROTECTED]> wrote:
> This is bordering on a way around the "static structure, dynamic
> content" vision! Not that we need to weasel around that vision to
> make great applications, but this is a way to have the best of both
> worlds--the performance of s
This is bordering on a way around the "static structure, dynamic
content" vision! Not that we need to weasel around that vision to
make great applications, but this is a way to have the best of both
worlds--the performance of semi-cached templates/classes with the
flexibility of live structure edi
This is precisely the stuff I've been working on for the past few weeks.
I too am successful with pulling templates from a DB and so far, so
good.
I'll need to dive back into the code to see if there's a way to do a
template parse and be able to catch an exception if there's an error.
in
dangerous ideas
This could be an interesting way of running an application straight
from a DB backend, where the DB can act as a versioning system if
needed. A new updated class or template is uploaded to the DB, and
the flushCache() causes the CTS service to pick up the newest template
versio
Obviously, we can't predict every possible use case ahead of time.
On Jan 16, 2008 2:56 PM, David Kendall <[EMAIL PROTECTED]> wrote:
> I would like to have a way to force tapestry to flush/reload its caches
> and I am wondering how best to get such functionality incorporated into
> the Tapestry
