Re: [Evolution-hackers] Subclassable and extendable IMAPX

2012-05-23 Thread Matthew Barnes
On Wed, 2012-05-23 at 18:40 +0200, Christian Hilberg wrote: > As dwmw2 just pointed out on IRC, it really isn't. > The data structures which the derivative untagged handlers > need to access can/should best be bound to the derivative > CamelIMAPXServer. In fact, that is exactly the way it works > i

Re: [Evolution-hackers] Subclassable and extendable IMAPX

2012-05-23 Thread Christian Hilberg
And again... Am Mittwoch 23 Mai 2012, um 18:40:34 schrieb Christian Hilberg: > Hi again, > > Am Mittwoch 23 Mai 2012, um 18:05:29 schrieb Christian Hilberg: > > Passing in the user payload data showed to be specifically tricky. > > As dwmw2 just pointed out on IRC, it really isn't. > The data st

Re: [Evolution-hackers] Subclassable and extendable IMAPX

2012-05-23 Thread Christian Hilberg
Hi again, Am Mittwoch 23 Mai 2012, um 18:05:29 schrieb Christian Hilberg: > Passing in the user payload data showed to be specifically tricky. As dwmw2 just pointed out on IRC, it really isn't. The data structures which the derivative untagged handlers need to access can/should best be bound to t

Re: [Evolution-hackers] Subclassable and extendable IMAPX

2012-05-23 Thread Christian Hilberg
Hi everyone, had a chat with Chen on IRC today about the topic. Since he had to leave, I'll try to sum up our findings here, for the record and for review, please see the inline comments. Am Mittwoch 23 Mai 2012, um 10:00:27 schrieb Christian Hilberg: > Am Dienstag 22 Mai 2012, um 16:38:20 schrie

Re: [Evolution-hackers] Subclassable and extendable IMAPX

2012-05-23 Thread Christian Hilberg
Am Dienstag 22 Mai 2012, um 16:38:20 schrieb Christian Hilberg: > Hi again, > [...] > Seems the solution which is now in Git master solves only part > of what is needed (or I am missing something, in which case I > will happily accept correction). Let me just drop a short summary of what we've com