] Proposal: Rename
AuthenticationDao interface
[EMAIL PROTECTED] wrote:
Thanks guys,
I'll propose we leave this open for comment one more
day and if there
aren't any objections I'm willing to make the code and
documentation
changes this weekend.
Scott
Hi Scott
Please
17, 2005 10:21 AM
To: acegisecurity-developer@lists.sourceforge.net
Subject: RE: [Acegisecurity-developer] Proposal: Rename
AuthenticationDao interface
+1 from me too. I think its better to break stuff now when we still
+have a
excuse (hey, it ain't 1.0 yet) than post 1.0.
-tim
+1
I support the change, it makes more sense to me.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Ben Alex
Sent: Thursday, November 17, 2005 9:23 AM
To: acegisecurity-developer@lists.sourceforge.net
Subject: Re: [Acegisecurity-developer] Proposal
: [Acegisecurity-developer] Proposal: Rename
AuthenticationDao interface
Ray Krueger wrote:
You currently have an AuthenticationDao that successfully returns a
UserDetails instance that is built up by your four database scheme
now, correct? The whole point of the AuthenticationDao
]
On Behalf
Of Ben Alex
Sent: Thursday, November 17, 2005 9:23 AM
To: acegisecurity-developer@lists.sourceforge.net
Subject: Re: [Acegisecurity-developer] Proposal: Rename
AuthenticationDao interface
Ray Krueger wrote:
You currently have an AuthenticationDao that successfully returns
-developer@lists.sourceforge.net
Subject: Re: [Acegisecurity-developer] Proposal: Rename AuthenticationDao
interface
lol Sorry Scott :)
When Ben puts it like that I gotta agree hehe.
+1
On 11/17/05, Dmitriy Kopylenko [EMAIL PROTECTED] wrote:
+1 also
Darrell Kundel wrote:
+1
I support the change
You currently have an AuthenticationDao that successfully returns a
UserDetails instance that is built up by your four database scheme
now, correct? The whole point of the AuthenticationDao is to build a
UserDetails instance, by whatever means necessary. So, no, users like
you should do exactly
Hi Scott,
From my perspective, I always saw the AuthenticationDao as just that... a pluggable interface for authentication data access (i.e.in-memory, jdbc, ldap, etc.)
I personally dont see this interface at a Service Layer level?
The AuthenticationProvider err.. provides a layer ontop of the
-Original Message-
From: Mark St.Godard [mailto:[EMAIL PROTECTED]
...
The AuthenticationProvider err.. provides a layer ontop of
the actual authenticatonDao, so maybe I am missing something.
Hi Mark!
Hmmm, it could be me that's been missing it. In my case where I need to hit
