Re: [Evolution-hackers] camel into eds

[Not Zed <notzed ximian com>]

> Does this mean simply moving the code into the e-d-s libraries, keeping
> the camel provider threads running in the main evolution process?

Definitely only moving for now.  Including perhaps a camel-core/mime vs provider split, perhaps (though that might not be worth it).

> Or do you envisage moving the camel provider threads into the e-d-s
> process, or perhaps better, into a new process? (e.g. camel-data-server)
> Maybe even one process per provider?

Maybe in the future, but its a long way off since it affects the client code significantly, and would require a lot of api to be useful too.  It would really have to be one process, for efficiency's sake, and for vFolders to work (unless you wanted them to talk via corba too, ugh), it could live inside eds or not.  It might not actually be that practical to ever do it.