On 1/21/02 4:14 PM, "Gonzalo A. Diethelm" <[EMAIL PROTECTED]> wrote:
>> By using this method, someone could use any security mechanism >> they wanted. >> They may be able to start simple if they want, even using a >> simple text file >> and they can evolve their security model as they need to or move >> to a model >> written by another. It might even be nice to allow many models to >> run in the >> same application so that other systems could be integrated or allow >> selective migration to other models. Maybe the SecurityManger could >> manage many security models and map them to a portion of your application >> using a policy or security region. > > This would be great! > >> Right now with the pipeline in place and functioning it would be >> possible to >> implement this system, and I think I could get the skeleton in there this >> week. > > That would also be great! Three things: > > * It would be very good if we could standardize on the names used for > different entities in the model: I have used User, Credentials > (password), Permissions, etc., others have used different terms. > Is there a standard we can follow? Sounds good. > > +1, and my offer to help you with anything you need. Let me know. We'll get a little more feedback on the list, then I would like to write up a little strategy and then it's all yours if you want it! Once we agree on a strategy if you and others want to implement it that would be great. Then I can move on to something else. >> Jason van Zyl > > > -- > Gonzalo A. Diethelm > [EMAIL PROTECTED] > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- 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]>
