On 1/24/02 2:50 PM, "Gonzalo A. Diethelm" <[EMAIL PROTECTED]> wrote:
> I'm attaching what are my ideas at this point; it is a really > small file (100 lines). Feel free to completely thrash it. > Again I think this is creeping into specifics. I would really like to start with the empty interfaces to make sure completely different models will be supported. Gonzalo, I know that my simple use case of using a properties file would be supported under your model but I want people to be able to do whatever they want. What becomes standard is a different case. If you what you and Dan come up with is highly flexible and most people use that by default then I think that would be great: if a set of tools were built around a particular model, say pluggable Authenticators or Authorizers that's cool but I still want people to be able to do whatever they want. Not even being forced to use the names of entities in specified in your first attempt at the interface. Even with the interface outlined it would take quite a bit of effort to allow Scarab or Sourcecast to use. I am still pushing for the empty interfaces to begin with. -- jvz. Jason van Zyl http://tambora.zenplex.org http://jakarta.apache.org/turbine http://jakarta.apache.org/velocity http://jakarta.apache.org/alexandria http://jakarta.apache.org/commons -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
