Le 23/02/2010 21:14, Timothy Perrett a écrit :
Seems like the current lift-ldap ought to be gutted and turned into a
pure LDAP wrapper for scala. Then we can add a record abstraction and
any other abstractions people want.
In my company, we are building an LDAP-based application with a web UI
haha yeah, well I was originally planning on writing a record backend in my
book for LDAP, but thought we already had one... so maybe i'll do it in a month
or two ;-)
Cheers, Tim
On 23 Feb 2010, at 20:46, Ross Mellgren wrote:
> Hah maybe if I have some extra moments I'll look at it. I'm prepar
Hah maybe if I have some extra moments I'll look at it. I'm preparing for a
short trip this weekend so my spare time this week is short.
If you didn't have a book to write I'd make you do it! ;-)
-Ross
On Feb 23, 2010, at 3:40 PM, Timothy Perrett wrote:
> Ross my good man, did you just volunte
Ross my good man, did you just volunteer? :-D
+1 on the MegaUberRobotTronFromOuterSpace. There is also a fair amount of
Java-ish code in there; it would be nice if that went away sometime too :-)
Cheers, Tim
On 23 Feb 2010, at 20:32, Ross Mellgren wrote:
> Perhaps eventually (or if someone rig
Perhaps eventually (or if someone right now has a strong use), but maybe in the
short term it should be just mildly split up a bit so that it can be used
separate of MetaMegaTron? I'm sure there are plenty of people who just need
authentication and have no intent of using more sophisticated LDAP
Seems like the current lift-ldap ought to be gutted and turned into a
pure LDAP wrapper for scala. Then we can add a record abstraction and
any other abstractions people want.
Cheers, Tim
On Feb 23, 8:07 pm, Ross Mellgren wrote:
> It might turn out that we'll need an actual LDAP record backend a
It might turn out that we'll need an actual LDAP record backend at work, so I
may write one in the future ;-)
-Ross
On Feb 23, 2010, at 3:00 PM, Timothy Perrett wrote:
> Oh yeah, you are right Ross!
> Doh... in that case, might have to do some refactoring on that module
> to give it a more func
Dick, that is exactly what I want also... I was expected the dude who
added it to lift to tidy it up and make it more abstract before adding
it to the project.
I would suggest have a base LDAP module (perhaps record based) and
remove the mapper stuff.
Cheers, Tim
On Feb 23, 8:01 pm, Dick Hirsch
Any chance that the LDAP functionality will be independent of
MetaMegaProtoUser and MegaProtoUser?
Or maybe some sort of guidance (how-to?) on how to use it without
these classes.
We've (Apache ESME) have been waiting for a while for LDAP to be
supported in Lift but we don't use MegaProtoUser.
T
Oh yeah, you are right Ross!
Doh... in that case, might have to do some refactoring on that module
to give it a more functional style.
Cheers, Tim
On Feb 23, 7:15 pm, Ross Mellgren wrote:
> There's no record code in there -- it uses mapper in fact.
>
> I think this is just for auth.
>
> -Ross
>
10 matches
Mail list logo