On Thu, Oct 03, 2002 at 12:16:53AM +0200, Simo Sorce wrote about 'Re: [PATCH] sam backend parameter': > yes a thing I'm not sure has ever been a good idea. > to be able to have sam2sam that is really read a backend + store all > info into another backend we may take several ways.
> We never need the 2 backend to be loaded at the same time to do the > operation, we may easily read all the accounts chnage the backend and > store them into the new one, or simply make custom code to load 2 > different backends, and use theyr calls. > It's easy to have 2 structures calle backend1 and backend2 that holds > the functon pointers for 2 backends. > Al the context things always seemed to me overcomplicated even for > multiple backend code. the context stuff has been in passdb since the beginning and is not at all used for multiple backends - multiple backends are achieved by having multiple 'methods' structs in one context. Next to that, a 'multidb' backend will have to use multiple contexts. We don't want to spoil global name space with the variables sam_context contains. If we are removing multiple domain support, we could remove sam_methods perhaps and move all the functions in sam_methods to sam_context, but sam_context definitely has to stay... Jelmer > On Wed, 2002-10-02 at 23:56, Jelmer Vernooij wrote: > > > - what is all the context thing needed for? > > Sometimes we need multiple contexts. For example, when doing sam2sam. > > Please notice that passdb has this as well... -- Jelmer Vernooij <[EMAIL PROTECTED]> - http://nl.linux.org/~jelmer/ Development And Underdevelopment: http://library.thinkquest.org/C0110231/ Listening to 07:18:45 up 12 min, 4 users, load average: 0.09, 0.05, 0.01
