[TransWarp] Multiapp multithreaded server and configurable services

Radek Kanovsky rk at dat.cz
Fri Jun 20 11:54:34 EDT 2003

On Fri, Jun 20, 2003 at 11:35:17AM -0400, Phillip J. Eby wrote:

> At 05:11 PM 6/20/03 +0200, Radek Kanovsky wrote:
> >But this ContactDM can have some classAttr (typicaly cache)
> >that canot be shared on 'app2:/dm1' and 'app1:/svc1/dm11' occurences
> >of ContactDM class. Obviously this components will be working on different
> >databases or tables and cannot share cache.
> The answer is simple: don't use per-class caches.  Why can't you cache 
> using instance attributes instead?  Or if you need some sort of 
> application-wide cache, why not define a utility for the cache, and have 
> the instances look it up and bind to it?

It could be the way but I want control caching per component. Some DM
can hold all database table in memory while other don't. One application
can have connection to more databases and oids can collide. And caches
are not all that case. There is demand for other serviceAttrs.


More information about the PEAK mailing list