Berin Loritsch wrote:
> I would like to propose a minimum set of attributes that all containers
> need to support, which will provide some guarantees for the components
> that need them. So far, I only have three that would fit the bill:
>
> 1) "context:dir" A java.io.File representing the context directory
> available to the component. Sort of a "home" directory.
Hmmm... What's the difference with context:scratch?
Persistence between invocations?
> 2) "context:scratch" A java.io.File representing the context directory
> that the component can use as a hash area--nothing permanent
> guaranteed, but useful for dynamic compilation, cache entries, etc.
context:tmp
context:temp
context:tempdir
context:temp.dir
> 3) "context:classloader" A java.lang.ClassLoader that the component can
> use to create objects or child components with.
Ok.
> The names are of course up for debate, but the concepts are fairly
> constant.
> I would like a standard set of names so that the components like
> SourceResolver
> can implement a "context:" protocol that maps to the home dir easily.
> It will also help with the cache implementations, et. al.
>
> Thoughts?
+1
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
