Leo Simons wrote:
> On Tue, 2002-09-17 at 23:07, Berin Loritsch wrote:
> 
>>Has two context keys defined an done attribute defined.  Obviously this
>>is not enough, but we need to get to the proper abstractions.  Anyway,
>>here are some changes that need to be performed:
>>
>>CONTEXT
>>
>>Key           Type                Description
>>-----------   ----------------    -------------------------------------
>>avalon:home   java.net.URL        This is a context directory that may
>>                                   contain a bunch of files that a
>>                                   component needs to do its work.  There
>>                                   is NO GUARANTEE that the URL is
>>                                   writable.
> 
> 
> +1
> 
> thought: "directory" implies use of file:/// as the protocol. Is that
> part of the contract?

Nope.  Consider the Servlet spec.  When you get a file/resource out of
the supplied context you are not guaranteed what its protocol is.  With
Tomcat, it happens to be the "file://" protocol, but with IBM WebSphere
it is "classloader://".

For containers that are embedded in a servlet environment like Cocoon,
we cannot assume "file://" will be the protocol--although nine times
out of ten it will be.

> 
> 
>>avalon:work   java.io.File       This is a work directory that the
>>                                  component may use as a work area.  This
>>                                  directory MUST be writable.
> 
> 
> +1
> 
> thought: we might want to add notions of isolation here as well (perhaps
> later on), in that it is guaranteed no other component will overwrite
> stuff here......

:)  That is the general idea.


>>avalon:name   java.lang.String   The name of a component (is this
>>                                  really necessary?)
> 
> 
> +1. Seems useful to me (wrt logging, GUIs, etc). Regardless, I doubt
> anyone would ever want to attach a different class or meaning to
> "avalon:name" so I doubt it will lead to problems.

Well, with logging the category can be assigned to the "avalon:name",
and management GUIs would have another way to access that information.
So my point is why would we need it to solve real problems?


-- 

"They that give up essential liberty to obtain a little temporary safety
  deserve neither liberty nor safety."
                 - Benjamin Franklin


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to