Re: [evolution-patches] patch for adding GW camel provider

[Rodrigo Moya <rodrigo ximian com>]

On Mon, 2004-01-05 at 09:44, Not Zed wrote:
> On Wed, 2003-12-24 at 17:30 +0100, Rodrigo Moya wrote:
> > Hi
> > 
> > Based on Sivaiah's patch sent last week, here's a patch for adding the
> > Groupwise provider to Camel. It doesn't work for me, since Groupwise
> > doesn't show up in the account types, but since I am leaving for
> > vacation today (I'll still check mail tomorrow) and will be back (2nd
> > January) after Sivaiah's (28th December) come back, I've:
> > 
> > * committed the camel/providers/groupwise files. The rest hasn't been
> > committed, to not include the provider yet in the build, until it works.
> > 
> > * debugged the loading of the provider, which needs the imap and smtp
> > providers loaded first in order to avoid undefined references. I tried
> > using g_module_open on those providers to have them loaded, but I'm
> > still getting the same problem.
> > 
> > * not committed the groupwise-listener class Sivaiah wrote, so that
> > needs to be committed and fixed.
> > 
> > have a nice holiday and see you next year
> 
> 
> 
> 
> Is the provider just using the imap provider and the smtp transport
> for implementation,
>
yes

>  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.

> 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?

> 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?

cheers