JMAP text/eventsource events #22

Open
opened 2 years ago by epilys · 2 comments
epilys commented 2 years ago
Owner

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/
epilys added the
JMAP
help wanted
bug
enhancement
labels 2 years ago
epilys added this to the release milestone 2 years ago
Poster
Owner

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.
epilys modified the milestone from release to async 1 year ago
epilys modified the milestone from async to (deleted) 1 year ago
epilys added this to the First class JMAP support project 1 year ago

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.
epilys started working 11 months ago
epilys stopped working 11 months ago
3h 23min 23s
epilys referenced this issue from a commit 11 months ago
epilys changed title from JMAP notifications to JMAP text/eventsource events 11 months ago
epilys removed the
bug
label 11 months ago
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Total Time Spent: 3h 23min 23s
epilys
3h 23min 23s
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.