I actually think some of those could go into a session based SiteUser object
- I typically put operations into a service method only if they relate to a
collection of objects or if an object instance doesn't yet exist (in which
case the service method or the DI engine has to handle it - one of the two).
Because that seems to me object specific, for know I put such code into the
service method rather than a generalized factory.

For example, I'd put changePassword() and hasRole() into the SiteUser
business object. Not always the right approach, but not a bad generalized
solution.

Best Wishes,
Peter


On 1/9/07 4:23 PM, "Aaron Roberson" <[EMAIL PROTECTED]> wrote:

> Peter,
> 
> I read your comments on Kevan's blog post. I like the idea of using
> the userService to delegate authentication to the
> userAuthenticationService as you mentioned. However, I am wondering if
> you would place all of the methods (isLoggedIn, login, logout,
> hasRole, and changePassword) in the userAuthenticationService?
> 
> I do appreciate Kevan's post and have a much better idea now of what I
> am needing to do. Thank you!
> 
> -Aaron
> 
> On 1/9/07, Peter Bell <[EMAIL PROTECTED]> wrote:
>> On 1/9/07 2:44 PM, "Kevan Stannard" <[EMAIL PROTECTED]> wrote:
>>> Any feedback from anyone on the list is appreciated.
>> 
>> Well, you asked! Nice blog, btw.
>> 
>> Best Wishes,
>> Peter
> 
> 
> You are subscribed to cfcdev. To unsubscribe, please follow the instructions
> at http://www.cfczone.org/listserv.cfm
> 
> CFCDev is supported by:
> Katapult Media, Inc.
> We are cool code geeks looking for fun projects to rock!
> www.katapultmedia.com
> 
> An archive of the CFCDev list is available at
> www.mail-archive.com/[email protected]
> 





You are subscribed to cfcdev. To unsubscribe, please follow the instructions at 
http://www.cfczone.org/listserv.cfm

CFCDev is supported by:
Katapult Media, Inc.
We are cool code geeks looking for fun projects to rock!
www.katapultmedia.com

An archive of the CFCDev list is available at 
www.mail-archive.com/[email protected]

Reply via email to