Aaron Stone wrote:
Paul J Stevens <[EMAIL PROTECTED]> said:
[snip] > Actually, some kind of UML redesign would really help
cleanup the code base (_ic_fetch, aarrrgh) and provide a better handle for
developing modules such as this. I know Dan was blasted for suggesting this,
but I happen to
Paul J Stevens <[EMAIL PROTECTED]> said:
[snip] > Actually, some kind of UML redesign would really help
> cleanup the code base (_ic_fetch, aarrrgh) and provide a better handle for
> developing modules such as this. I know Dan was blasted for suggesting this,
> but I happen to agree with him on
Paul J Stevens <[EMAIL PROTECTED]> said:
> Initialisation of the char** values seems a bit rough, esp in the
> __auth_get_ function which are the real workhorses of this module.
> I don't see any allocation going on there at all, which explains some
> of the trailing garbage I get from calls like
Ilja Booij wrote:
We have a need for LDAP in the neartime future as well, so it's high
priority work for us as well.
Great, so maybe we can share the load on this...
I've started building a small test suite for validating and testing this module.
Looks fine so far. Of course the first bug
Paul J Stevens wrote:
I'm digging into this as we speak. The whole auth layer is not really
about authentication at all, or at least not *just* about
authentication. It's too bloated for that. Calling it dbmailUser, or
something alike, would probably cover it better Actually, some
kind of
Hi Ilja,
> On the other hand... It's probably more useful to release first, and fix
> LDAP support later. LDAP is a big thing, and might better wait until
> after release.
Yes - there are always new features/enhancements/what-ever that would be
nice to have in 2.0 but if everything is accepted
I'm digging into this as we speak. The whole auth layer is not really about
authentication at all, or at least not *just* about authentication. It's too
bloated for that. Calling it dbmailUser, or something alike, would probably
cover it better Actually, some kind of UML redesign would reall
Ilja Booij wrote:
Aaron Stone wrote:
Ilja Booij <[EMAIL PROTECTED]> said:
I'd like to release 2.0rc8 (yes, flawed release engineering etc, no
need to discuss that right now I think) tomorrow, August 17th (at
about 4pm CET(=3pm GMT)). I'm not aware of any issues that should be
resolved a
Aaron Stone wrote:
Ilja Booij <[EMAIL PROTECTED]> said:
I'd like to release 2.0rc8 (yes, flawed release engineering etc, no need
to discuss that right now I think) tomorrow, August 17th (at about 4pm
CET(=3pm GMT)). I'm not aware of any issues that should be resolved at
the moment. am I c
Aaron Stone wrote:
Dan Weber <[EMAIL PROTECTED]> said:
Pidfile stuff needs heavy cleanup. Its overbloated and
overcomplicated. It breaks the one best rule of programming: Make your
Code Concise and Orthogonal.
It's taken from Samba, seems to work for them. Concise it may not be, bu
10 matches
Mail list logo
