[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: VFS cache as impl detail, to what extent

[alesj]

Moving Dimitris' comment here.

"dimitris at jboss.org" wrote : 
  | From the outside I understand that caching should be an internal implementation detail/optimization non visible to the standard user or accessible over the simplified api.
  | 
  | Before we had URLs, everybody knew how they worked, server was working, there was nothing to configure, everyone was happy. With VFS we have started talking about cashing and weird options, and locking problems and threads and reapers and timeouts and what not. This is a step back, not forward. Some of it might be necessary, but it should be mostly invisible to the end user.
  | 
  | The whole point is: we need to make it *simpler*. It has to be stable and fast for 80% of the cases. Our users shouldn't even know it exists - they shouldn't care and they shouldn't have to tinker with bean descriptors to make it work for them, except for rare circumstances.
  | 
  | That would make a successful design. 
  | 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203965#4203965

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203965