2 ms·
Having used a JMAP-style API for years, it works really nicely with batching in a way that other APIs I've worked with don't. Of course, as one of the original
by brongondwana 9y ago
Having used a JMAP-style API for years, it works really nicely with batching in a way that other APIs I've worked with don't. Of course, as one of the original designers of JMAP, I'm bound to like it.
It would be quite easy to write a REST mapping for people who like more chatty protocols of course.
I'm not a giant fan of Foo/get either - it's a very recent change from the previous getFoos|setFoos|getFooUpdates naming, and there are pros and cons of the change. I try not to interfere too much with stylistic details like that though.
- Shoothe 9y agoThanks for the context! Are there intentions to standardize JMAP under IETF?
- brongondwana 9y agoI'm literally RIGHT NOW writing up an email to the IETF EXTRA mailing list, following up from the email I sent as co-chair to the IETF JMAP mailing list about conflicts for our session in London at IETF101 in March. We've been working inside the IETF on JMAP since Chicago (IETF98) in March last year.
- Shoothe 9y agoExcellent! Is there a place to look for progress on this front? IETF mailing lists? jmap.io?
- brongondwana 9y agoWe're keeping jmap.io up-to-date with the latest spec (including the calendar and contacts bits - calendar is partially underway through ietf calext - contacts are not yet on standards track) Also: https://datatracker.ietf.org/wg/jmap/about/ https://datatracker.ietf.org/wg/jmap/about/ Has links to the latest revisions of the drafts - and to the github repo where issues are being tracked.
- Shoothe 9y agoThanks a lot! I really appreciate it.