Re: [evolution-patches] patch for camel groupwise provider and config listener
- From: Rodrigo Moya <rodrigo ximian com>
- To: Not Zed <notzed ximian com>
- Cc: Siva <snallagatla novell com>, evolution-patches ximian com
- Subject: Re: [evolution-patches] patch for camel groupwise provider and config listener
- Date: Fri, 09 Jan 2004 16:46:42 +0100
On Fri, 2004-01-09 at 09:22 +1030, Not Zed wrote:
> >
> > From: Siva <snallagatla novell com>
> > To: evolution-patches ximian com
> > Subject: [evolution-patches] patch for camel groupwise provider and
> config listener
> > Date: Thu, 08 Jan 2004 19:07:07 +0530 (Fri, 00:07 CST)
> >
> > Hi,
> > I am attaching a patch which has a camel provider for groupwise.
> > groupwise camel provider juset uses IMAP for it provider store and
> SMTP
> > for its transport.
>
> So as discussed earlier, this is totally the wrong place to put this
> code.
>
> A camel provider is the lowest-level camel remote object, it shouldn't
> be managing other stuff. If you want meta-accounts, it should be
> managed elsewhere, although I don't know where it would fit, it
> doesn't even fit in the mailer as such. e.g. its no different from
> having a ldap configuration controlling mail + calendar for you.
>
right, the current account management for non-mail things suck
currently, but we decided to do it the camel way, like the Exchange
connector, since that seemed a better place, given that the other
solution was to have a separated config control only for groupwise.
Of course, we need to address this for post-2.0, so that we don't have
to write camel providers for bugzilla calendar backends, for instance.
> Anyway i'll comment on the patch itself, since it has bugs anyway.
>
Sivaiah, please correct those and submit a new patch.
cheers
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]