Unger Richard wrote: > > Hi! > > I really need to get the names sorted out before I can continue working... > > I like the name Authenticate and SlideStoreAuthenticateImpl . I think it > fits well with the rest of the helper class model. I also do not think that > this will dilute the separation between authentication and authorization, as > you seem to fear. All things concerning permissions and checking thereof > will remain in the Security Helper. Only the storage of the users, roles and > groups is handled by the authenticate helper, which makes some kind of > sense. > > As for RoleContainer, I really have been trying, but I can't seem to come up > with a better name for it. The name has to capture the idea, of course, that > this is an object to which roles can be assigned. RoleAssignee has been the > closest alternative I have come up with, but that does not seem better. > > So, unless I receive a better suggestion for the above, I will proceed with > this nomenclature. > > Let me know, esp. Michael, as you seem to be very opposed to 'Authenticate'. >
Right. Slide doesn't do authentication. Ever. So calling it that is a terrible idea. What slide _does_ (or can) do, is store a database of users for the servlet container to use for authentication. Getting the names reasonable is a fairly trivial thing, but misnaming them will make the code difficult to understand and hard to maintain. What you're calling "SlideStoreAuthenticateImpl" is a container for holding users (and groupings of users - either groups or roles), so calling it "SlideUserDatabase" or something along those lines would make MUCH more sense. Mike p.s. sorry for the late reply, had exams this week. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
