-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 22 Feb 2006, Nathan C. Smith wrote: > We need to impose a feature freeze and get the .2 release out. There are a > lot of great ideas coming now but we can't incorporate them all into the .2 > release.
Decide a date for a feature freeze, and if we can get the plist stuff by then it should go in. > Some other good points have been made about real-time and LDAP and "user > objects". These ideas keep popping up. Has anybody given much > consideration to what a user object should encompass? Have you written it > down anywhere to share? :) I think we all *think* we know what a user > should include but somebody should try to write it down so we can give it > further consideration. A user may need to be stored in LDAP, relationally > or as a flat-file record and be flexible enough to adapt to future needs. > We should start considering these questions now in case somebody reaches > this point in their branch or wants to run with it. The user stuff by itself could be very simple, just an extension and a pin-code perhaps, that would work for the apps that require auth. Users for iax/sip/etc are a bit more complicated tho. I'll think about it and see if I can write up a proposal. /B - -- * GPG-Key: http://evil.gnarf.org/mrbk.pgp A: Because we read from top to bottom, left to right. Q: Why should i start my reply below the quoted text? - -- http://www.i-hate-computers.demon.co.uk/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFD/IrpckvkFeO3ANARAgGFAKCgLcN2QBLPNRcewpqCmgEpQBWdZACdEud3 FFxrZL/UkE0wYQ2gv9oBLNw= =zmfi -----END PGP SIGNATURE----- _______________________________________________ Openpbx-dev mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-dev
