>>>>> "Francisco" == Francisco Lozano <[EMAIL PROTECTED]> writes:
Francisco> Couldn't this be solved by creating temporary files
Francisco> containing the data from the ldap and then making the
Francisco> programs get their data from those temporary files?
Francisco> could this make qmail-ldap developers happy enough to
Francisco> include the ldap- control in the main tree?
Then you're back to FS files... The whole point was to get rid of them...
If you'd like it this way, you could write a script that extracts all
the configs and put them in it's default location on disk, and don't use
the QmailLDAP/Controls patch...
Francisco> I really don't see the problem with the way it
Francisco> currently works...
Neither do I. Henning 'complained' tough, saying it didn't work for him.
He's using a _BIG_ (read: _HUGE_ site) from what I understand. He got to
much trafic between Qmail and the LDAP server...
Francisco> Come on guys, even there is a DNS server which answers
Francisco> from LDAP resources and gets the registers from the
Francisco> LDAP tree on EVERY query (no caching) and the
Francisco> performance really rocks... I just can't see the
Francisco> problem with the current qmail- ldap-control way of
Francisco> working. The LDAP is a fast-search database, or at
Francisco> least it was designed to be so...
The problem get's worse when you receive/deliver _HUGE AMOUNTS_ of mails
every second. I don't know exactly WHERE the threshold is, but a guess
would be a couple of thousand (?) mails per minute... I don't get THAT
much mails on my site(s), so I don't know.
--
colonel munitions PLO Waco, Texas bomb domestic disruption FBI
Khaddafi Peking NSA Kennedy Honduras Iran cryptographic tritium
[See http://www.aclu.org/echelonwatch/index.html for more about this]
