JMAP text/eventsource events #50

Closed
opened 2020-04-05 23:51:35 +03:00 by Manos Pitsidianakis · 2 comments

Copying comment from #7:

I have contacted fastmail support about their JMAP notification endpoint. Here's part of the help ticket that describes the problem:

epilys writes:

According to rfc8620 the Session object returned by a
JMAP server must contain an eventSourceUrl field that
contains the url...:

" The URL to connect to for push events, as described in
Section 7.3, in URI Template (level 1) format [RFC6570].
The URL
MUST contain variables called "types", "closeafter", and
"ping".
The use of these variables is described in Section 7.3."

[..] Right now I'm connecting to jmap.fastmail.com and the
eventSourceUrl is "https://jmap.fastmail.com/event/" [..]

Resources

Copying comment from #7: I have contacted fastmail support about their JMAP notification endpoint. Here's part of the help ticket that describes the problem: > ***epilys writes***: > > According to rfc8620 the Session object returned by a > JMAP server must contain an eventSourceUrl field that > contains the url...: > > " The URL to connect to for push events, as described in > Section 7.3, in URI Template (level 1) format [RFC6570]. > The URL > MUST contain variables called "types", "closeafter", and > "ping". > The use of these variables is described in Section 7.3." > > [..] Right now I'm connecting to jmap.fastmail.com and the > eventSourceUrl is "https://jmap.fastmail.com/event/" [..] ## Resources - https://docs.rs/eventsource/ - https://jvns.ca/blog/2021/01/12/day-36--server-sent-events-are-cool--and-a-fun-bug/
Manos Pitsidianakis added the
JMAP
help wanted
bug
enhancement
labels 2020-04-05 23:51:35 +03:00
Manos Pitsidianakis added this to the release milestone 2020-04-05 23:51:43 +03:00

UPDATE: Fastmail support has replied:

So, it appears push is not implemented yet for our
public JMAP endpoint. I have now created an internal
task for our developers to look into this. I am afraid,
I don't have a timeline on this at the moment, sorry.

I will implement polling until there's a better solution.

UPDATE: Fastmail support has replied: > So, it appears push is not implemented yet for our > public JMAP endpoint. I have now created an internal > task for our developers to look into this. I am afraid, > I don't have a timeline on this at the moment, sorry. I will implement polling until there's a better solution.
Manos Pitsidianakis modified the milestone from release to async 2020-06-29 19:49:36 +03:00
Manos Pitsidianakis modified the milestone from async to (deleted) 2020-09-19 14:31:26 +03:00
Manos Pitsidianakis added this to the First class JMAP support project 2020-10-16 15:03:12 +03:00

just wanted to mention how cool it is you support jmap and even push the fastmail team to do better. Loving meli and looking forward to offline jmap support and all you can add.

just wanted to mention how cool it is you support jmap and even push the fastmail team to do better. Loving meli and looking forward to offline jmap support and all you can add.
Manos Pitsidianakis started working 2021-01-05 15:53:43 +02:00
Manos Pitsidianakis stopped working 2021-01-05 19:17:06 +02:00
3h 23min 23s
Manos Pitsidianakis changed title from JMAP notifications to JMAP text/eventsource events 2021-01-05 20:16:46 +02:00
Manos Pitsidianakis removed the
bug
label 2021-01-05 20:16:56 +02:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: meli/meli#50
There is no content yet.