~sircmpwn/aerc2#15: 
Add JMAP worker

Status
RESOLVED WONT_FIX
Submitter
~sircmpwn
Assigned to
No-one
Submitted
2 years ago
Updated
1 year, 7 months ago
Labels
feature

~sircmpwn REPORTED WONT_FIX 1 year, 11 months ago

~rumpelsepp 1 year, 11 months ago

delayed or won't happen?

~sircmpwn 1 year, 11 months ago

Won't happen.

~alexmo 1 year, 8 months ago

I don't know what is meant by worker, but does that mean there will be no jmap support at all?

~sircmpwn 1 year, 8 months ago

No, there will not be JMAP support.

~svmhdvn 1 year, 8 months ago

Would you be able to clarify why you've chosen to not have JMAP support? I'm just curious, since it seems like a beneficial feature.

~ernierasta 1 year, 7 months ago

I think I understand why it is rejected, I suspect:

  1. Server support is currently weak, mayby cyrus is best choice?
  2. We have no JMAP client library in golang.
  3. RFC out of draft for just few months (August 2019) and Calendar and Contacts standards are not done yet.
  4. I do not read specs, but maybe logic is so different, that it would mean many changes (even in UI) of aerc?

If we have working, tested JMAP client library in golang ... this would be nice.

But I do not know reasons Drew have.

Register here or Log in to comment, or comment via email.