Re: JMAP protocol: Implementing RFC-8620 & RFC-8621

2019-09-17 Thread Tellier Benoit
I updated https://issues.apache.org/jira/browse/JAMES-2884 accordingly to what had been discussed in this thread. I did also create a first batch of sub-tasks to reflect the first steps of the aforementioned approach. Concretely, the first target is: Getting a 'memory-guice' powered 'jmap' serve

Re: JMAP protocol: Implementing RFC-8620 & RFC-8621

2019-09-16 Thread Tellier Benoit
On 16/09/2019 15:38, Matthieu Baechler wrote: > Hi, > > On Mon, 2019-09-16 at 10:19 +0700, Tellier Benoit wrote: >> Hello all, >> >> [...] >> >> What would you think of such an approach? >> > > There's a small detail that bothers me: in the past, relying for too > long on in-memory only made the

Re: JMAP protocol: Implementing RFC-8620 & RFC-8621

2019-09-16 Thread Matthieu Baechler
Hi, On Mon, 2019-09-16 at 10:19 +0700, Tellier Benoit wrote: > Hello all, > > @cketti mentioned his interest for helping updating our JMAP > implementation to final RFCs. Awesome > We should be careful not breaking things for existing James clients > using the deprecated/outdated JMAP specifica

Re: JMAP protocol: Implementing RFC-8620 & RFC-8621

2019-09-16 Thread Tellier Benoit
Hi Antoine, The proposal to expose the jmap protocol and jmap-draft proptocol on different port was to avoid "clash" and confusion on other endpoints (upload, download, authentication). I tend to find the "full separation" more clear. Having different port/maven module will also lead to two disti

Re: JMAP protocol: Implementing RFC-8620 & RFC-8621

2019-09-15 Thread Antoine Duprat
Hi Benoit, Seems great to me: don't break existing things. Don't you want to introduce a new endpoint for jmao-draft. That way with versions of the protocole might be bringed by the same product, and you let the choice of the client to use what endpoint he wants. An other point is about the name

Re: JMAP protocol: Implementing RFC-8620 & RFC-8621

2019-09-15 Thread rcordier
Hi, I agree to move forward with this. Rene. Sep 16, 2019, 10:19 by btell...@apache.org: > Hello all, > > @cketti mentioned his interest for helping updating our JMAP > implementation to final RFCs. > > We should be careful not breaking things for existing James clients > using the deprecated/

JMAP protocol: Implementing RFC-8620 & RFC-8621

2019-09-15 Thread Tellier Benoit
Hello all, @cketti mentioned his interest for helping updating our JMAP implementation to final RFCs. We should be careful not breaking things for existing James clients using the deprecated/outdated JMAP specification. Maybe the best thing would be to expose the final JMAP spec on an other port