I don't understand why having a generic cache interface would be bad. I
think Castor should provide some common cache implementations (FIFO, LIFO,
LRU, LFU,...), but give the application developer the freedom to develop
their own cache. This way if an application requires special caching
needs, then the developer could provide that functionality.
I think that this would allow for some one to also develop a distributed
cache to this same interface, satisfying this threads discussion. Castor
would not know what kind of cache is implemented, only that it is a cache
(very similar to JDBC, JNDI, Logging,...).
What does everyone else think?
Adam
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
