On Thursday, January 24, 2019 at 11:41:50 PM UTC-6, Bron Gondwana wrote: > > You're welcome. Thanks for the blog post. It's great to see implementation > experience from people who haven't been working with this stuff for years! > > I'll be taking about JMAP at fosdem next weekend, and I'll definitely > mention how easily you were able to convert from IMAP to JMAP in your > client. > Thanks for considering my feedback!
My estimate is 40 hours of work to build an IMAP compatible JMAP interface (for my client software). Another 3 hours to build the UI management to add/delete JMAP servers and split them out from IMAP sources. Cypht already separates data sources from authentication, so adding a new source is a lot easier than it might be with a traditional webmail client. Our IMAP library is 3036 lines of code, the JMAP compatible version is 861 lines (both counted as NCLOC) which is pretty impressive considering I'm not yet leveraging the real strengths of JMAP yet. I have been working on webmail development for a LONG time, and I have to say, supporting JMAP was not just a lot easier than I thought it would be, It is genuinely enjoyable! Jason -- You received this message because you are subscribed to the Google Groups "JMAP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jmap-discuss/da22039e-5cc5-4120-b727-061053d9c5b3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
