RE: [Springframework-developer] Road map (security)

[<ad...@tr...>]

On 03-12-2004 10:18 +0000 sam...@ma... wrote:
> Looking at Spring as a relative newcomer, I can see that in Spring itself
> there is already support for a wide number of API's and technology, any
> of which could be in separate projects. Persoanlly, I prefer being able
> to download one big bundle then pick and choose what I use. Your project
> will certainly be of use to people, and having it inside Spring as a
> fully supported API adds to Spring as a whole - it will also lead people
> to think it will have a certain level of quality in line with the rest of
> the Spring code. I have no objections to it being included, but as a
> non-commiter its not reall my place to say...

I'd like to chime in here as well. One of the most valuable facets of=20
Spring for me has been the quality of the developers working on it. When=20
trying to evaluate how to approach a problem domain, it gives me lots of=20
confidence if the developers on this list have looked at a solution and=20
approve of it being in Spring core.

For example, Ben's security framework looks great to me. But I know that if =

Rod, J=FCrgen, Alef, etc, have looked at it and think it is solid then it=20
probably is. I guess I like to borrow the knowledge of the more experienced =

developers.

In conclusion, it is always a good idea to keep the framework flexible=20
enough that people can do whatever they please. However, having "approved"=20
implementations of certain capabilities, like security, is important.

My 2 cents.

A.

--=20
Adam Sherman
Tritus CG Inc.
+1 (613) 797-6819
http://www.tritus.ca/