Re: Mysql Support Patch (mailutils)

[Alain Magloire]

> 
> > I think, it's a great idea.
> > Then we came move some of the code commited, by Jakob to use the
> > same technique.
> 
> Done. I didn't move Jakob's code in imap4d/login.c, though. There
> are two possible approaches to it: either a chain of user-defined
> getpwnams, or a single getpwnam that would do the job. Using the
> first approach one would do in imap4d:
> 
>     #ifdef HAVE_MYSQL
>       mu_register_getpwnam (getMpwnam);
>     #endif
>     #ifdef USE_VIRTUAL_DOMAINS
>       mu_register_getpwnam (imap4d_virtual);
>     #endif
> 
> Using the second approach, one would need to supply a function that
> calls getMpwnam and imap4d_virtual in succession, and then register this
> function with mu_register_getpwnam. I'd vote for the former approach.
> Opinions?
> 

Same here, because it is the same technic we use when registering mailboxes.

/* register the desire mailboxes formats.  */
{
  list_t bookie;
  registrar_get_list (&bookie);
  list_append (bookie, mbox_record);
  list_append (bookie, path_record);
  list_append (bookie, pop_record);
  list_append (bookie, imap_record);
}

It looks different, because the list_t object managing the link list
is exposed.

But probaly I could cover this to have some consistency:

/* register the desire mailboxes formats.  */
{
  mu_register_mailbox (mbox_record);
  mu_register_mailbox (path_record);
  mu_register_mailbox (pop_record);
  mu_register_mailbox (imap_record);
}

I kind the like, the old way of forcing you to get the list, but ...
It may not be wise 8-).

--
alain