On 15-May-2001 Dave Palmer wrote:
> In playing with the whole pop3 external authentication, wouldn't it be cool
> if XMail had (in a future version) an open "api"?
> The idea is, take the implementation details out of certain areas of XMail
> and have an interface where a hacker could just
> plug in the details... this would be very nice for user management. For
> example, I wrote a java app that queries our Oracle
> database (where our employee information is stored... like passwords) so we
> don't have all these different places where user
> information is stored. It would be cool if you could write your own
> implementation of how and where user information
> is stored.
>
> There could be an api for java (heh heh), perl, c++ (duh) and tcl and maybe
> even a com version. By default xmail would ship with
> the standard implementation so that non-hackers could easily setup xmail and
> use the current method for user management.
>
> I dunno, it would certainly make XMail "open" to complete systems
> integration.
>
> okay... shoot this one down
Pls wear the helmet :)
The reason of my NO tp Your request is coz 95% of XMail users are not
programmers but system administrator that feel way more confortable to write
scripts instead of shared libraries ( .so or .dll ).
The information that these hooks has to return is also so simple ( an integer )
to not require an API.
- Davide
