On 7/13/05, Borislav Sabev <[EMAIL PROTECTED]> wrote: > How do you classify Security and Authorization issues in this metaphor? > > In my current project I have troubles since code that is related somehow > to Authorization is spread over all "rings. Still it's difficult to me > to have a clear understanding how to implement in a nice, consistent > way. I'll appreciate any suggestions or recommendations about this problem.
The classic Layers pattern describes a systems layer that runs along all the layers, so that it is adjacent to each one. Many Struts applications run into this problem not only with authorization but with validation. We often want to have some validation on the client-side, to enhance the user experience and to reduce load on the server, but, we can't do all the validation client-side, because there are things that only the server can know. (Like if the credentials tendered are valid.) -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
