You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "René Cordier (Jira)" <se...@james.apache.org> on 2020/03/06 09:23:00 UTC
[jira] [Created] (JAMES-3092) Implement a JMAP meta project to
redirect towards the correct JMAP implementation
René Cordier created JAMES-3092:
-----------------------------------
Summary: Implement a JMAP meta project to redirect towards the correct JMAP implementation
Key: JAMES-3092
URL: https://issues.apache.org/jira/browse/JAMES-3092
Project: James Server
Issue Type: Improvement
Reporter: René Cordier
`Currently`: JMAP draft server implemented base on serverless-Jetty and served it only.
`What we expected`: Served both `Jmap draft` and `Jmap-rfc-8620` implementation versions in `reactive server`.
`Proposal`:
- Reuse of work from [Refactoring jmap-draft to be reactive with reactor-netty](https://ci.linagora.com/linagora/lgs/openpaas/james/issues/1638).
- Server will served 2 implementations via `header filter` configuration for incoming request:
{code:java}
Accept: application/json;jmapVersion=draft` for jmap draft implementation version.
Accept: application/json;jmapVersion=rfc-8620` for `jmap-rfc-8620` implementation version.
{code}
- Implementation [jmap-rfc-8620](https://tools.ietf.org/html/rfc8620) into separate module by suggested name:
`org.apache.james.jmap.rfc-8620`
*DoD*: memory integration tests about version handling
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org