On Wed, 2011-09-14 at 16:43 +0200, Christian Hilberg wrote:
> Please forgive me for not reading the Camel code here - can one guess
> from the UID to which account it may belong?
Yes, in fact it's trivial now: CamelService.uid == EAccount.uid
> What's more, in the current evolution-kolab design
Hi there,
I know it is muc hlate for input, but anyway, here we go:
Am Donnerstag 21 April 2011, um 18:43:27 schrieb Matthew Barnes:
> To help smooth the way for the account-mgmt I've made a few improvements
> to the CamelSession and CamelService APIs in 3.1. It's not necessarily
> the *final* A
On Fri, Apr 22, 2011 at 5:54 PM, Matthew Barnes wrote:
> On Fri, 2011-04-22 at 11:02 +0530, Srinivasa Ragavan wrote:
>> Mostly sounds fine to me as a complete picture, but do remember of
>> the email-factory branch that I'm working on to run mail on EDS.
>>
>> I now expose an API (and some custom
On Fri, 2011-04-22 at 11:02 +0530, Srinivasa Ragavan wrote:
> Mostly sounds fine to me as a complete picture, but do remember of
> the email-factory branch that I'm working on to run mail on EDS.
>
> I now expose an API (and some custom bits) over dbus that corresponds
> to camel's session/store
Hey Matt,
On Thu, Apr 21, 2011 at 10:13 PM, Matthew Barnes wrote:
> To help smooth the way for the account-mgmt I've made a few improvements
> to the CamelSession and CamelService APIs in 3.1. It's not necessarily
> the *final* APIs that will wind up in 3.2, but more like the first round
> of ch
