Howdy, >> >1) Add a method 'List getSecurityConstraints(HttpRequest req, Context >ctx)' >> >to Realm, and have AuthenticatorBase loop through them. >> >2) Have RealmBase create it's own special SecurityConstraint that is the >> >intersection of all of the overlapping constraints, and leave >> >AuthenticatorBase alone. >> > >> >Case 1 has the advantage of being relatively clean from a coding >standpoint. >> >Case 2 would probably require adding a 'void intersect(SecurityContraint >> >sc)' method to the SecurityConstraint class to enable it to construct >the >> >correct permissions (and this looks like it would be a non-trivial >method >to >> >implement). >> > >> >Comments/Opinions/Flames?
I like the first approach better: +1 on that. Maybe use a Set instead of a List as they're supposed to be unique and order-independent, but that's a nitpick. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
