Comment 9 for bug 1421923

Hey Niklas.

Awesome work on this so far, you have made great progress!

I have a couple of questions/suggestions:

firstly for the created url that is sent through url-dispatcher. It would be great if it could be and rfc 5092 [1] compliant IMAP url. Particularly because this is the standard for referencing objects on a remote IMAP server but it also includes some useful info like the UIDVALIDITY which ideally a client should be checking, to be sure that the UIDs have not changed between the poll session and the new session created from the dispatched url.

Also in terms of how Dekko works it would be really helpful if the message partid was included as well, so that we would have a direct pointer to the exact message part you created the notification from. Which we can directly fetch and not have to parse the mime structure again to find the interesting part.

Secondly, I read you blog post but it wasn't entirely clear to me how a user will select the client to consume the notifications. IIRC url-dispatcher was recently made clever and if more than one app is registered to consume the same protocol/scheme then the user is prompted to select which app to use. Would it make sense to just utilize that? This is the current state for the mailto: protocol so it would make sense to keep it consistent. What's your thoughts?

Keep up the great work!

[1] https://tools.ietf.org/html/rfc5092