Re: [evolution-patches] patch for adding GW camel provider
- From: Rodrigo Moya <rodrigo ximian com>
- To: Not Zed <notzed ximian com>
- Cc: Evolution Patches <evolution-patches ximian com>, Sivaiah Nallagatla <snallagatla novell com>
- Subject: Re: [evolution-patches] patch for adding GW camel provider
- Date: Tue, 06 Jan 2004 12:35:45 +0100
On Tue, 2004-01-06 at 03:30, Not Zed wrote:
> > > what is the groupwise bit for? Why not just setup
> > > an imap account with a matcihng smtp server?
> > >
> > we need to create ESource's for calendar, tasks and contacts when you
> > create Groupwise accounts, that's the reason for this provider.
>
> So you're going to have the camel provider creating calendar, task and
> contact stuff? Couldn't it just be a different account setup wizard
> which implictly creates imap+smtp, and the esources?
>
well, then it would be separated, which we were trying to avoid. We
first thought about having a separated config control for that, but then
we thought it will look better if it was integrated with the other
accounts setup.
> > > I don't get it.
> > >
> > > Anyway you shouldn't use the imap and smtp symbols directly, just open
> > > the imap and smtp CamelProvider[s], and then peek in there for various
> > > info. Otherwise you wont pick up changes to config etc.
> > >
> > what do you mean? We should use the g_module to access the providers
> > directly?
>
> No, you should definetly not use g_module at all. You should use
> camel_session or camel_provider calls, i can't remember the entry points
> off the top of my head.
>
ok, looking into that. Please Sivaiah, have a look.
> > > I'm kind of sketchy on whether this approach will even work though.
> > >
> > what would work then? Providing a camel-groupwise-* version of all
> > needed classes, making them just subclass IMAP/SMTP classes?
>
> No you can't really do that either because of they way they are loaded.
>
> I'm still not clear on what you're trying to do. It sounds like a meta-
> account hwich just sets up all the other stuff for you, but you don't
> need a custom provider for that.
>
that's exactly what we want, a meta-account setup. The reason to have a camel
provider is to have that setup integrated with the other mail accounts,
since GW users will use the GW server for mail, contacts, and calendar.
cheers
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]