"Kelvin Tan" <[EMAIL PROTECTED]> writes: > Do you anticipate any problems with implementing it in Torque then, based on > the concern raised below? > >> However, due to the way Torque's business objects are created, >> after the business objects have been returned to the calling code, >> a cache is effectively useless since invoking something like >> book.getAuthor() basically makes a direct database request, >> bypassing the cache (_unless_ the cache sits between the objects >> and its peers, which would make it pretty Torque-specific and >> involve extensive modifications to Torque code, I think).
The caching service will be written stand-alone, then added as a layer between Torque and the database. I am willing to help with this modification. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
