Max Mazurov
Max Mazurov
Note to self: go-imap-namespace needs updating for the new Interface
Note to self: SendUpdate might need synchronization.
Another note to self: Need to somehow workaround sending of updates in response to CLOSE. This is potentially harmful deviation from RFC 3501.
TODO: Documentation should be cleaned from Updater, etc references.
Just rebased it onto master. If we synchronize dev with master conflicts should be gone.
go-imap extensions system is a kind of mess. It is hard to extend existing commands, I think this we might want to reconsider how it should work, taking into account...
>Agree. Do you think we should implement everything in go-imap itself? Not sure. I'm afraid this will require all go-imap server backends to support all extensions. Making it harder to...
>Not sure. I'm afraid this will require all go-imap server backends to support all extensions. Making it harder to implement at least minimal backend. On the other hand... Probably it...
Here is a challenge then: UIDPLUS and CONDSTORE extensions are on. How go-imap should interact with backend to make use of them (interfaces?) How backend interface should look without these...
I guess backend methods like CreateMessage need support for arbitrary opaque inputs and outputs. Like, response with COPYUID information, etc. As I said: >Something similar to opaque FetchItems and StatusItems...