4 ms·
https://jmap.io/#push-mechanism https://jmap.io/#push-mechanism JMAP going to use rfc8030 push for mobile (3rd party service for notifications, really?) and Eve
by Nasreddin_Hodja 7y ago
https://jmap.io/#push-mechanism https://jmap.io/#push-mechanism JMAP going to use rfc8030 push for mobile (3rd party service for notifications, really?) and EventSource (kind of http long polling) for desktop clients, as I understood. I don't like that idea, it's even worse than IMAP4 IDLE. Why not just WebSockets for mobile and desktop clients?
Or just building it on top of XMPP protocol (or any other chat protocol).
- nailer 7y agoHTML5 Server Sent Events are better than long polling, and they're about as old as websockets, but simpler, as they maintain the concept of HTTP resources whereas websockets replace the concept. HTML5 SSE is also easier to implement. Not hating on websockets, but saying HTML5 SSE is outdated tech is just wrong. If you were making a real time app that works over HTTP either would be fine.
- Nasreddin_Hodja 7y ago> HTML5 Server Sent Events are better than long polling But it works the same way: infinite http connection.
- wchest 7y ago> The JMAP protocol is transport agnostic and can be easily transported over a WebSocket, for example, as well as HTTP From section 10. of the jmap.io link you referenced. I haven't used JMAP or looked into the spec in any detail, but wanted to provide that context for anyone coming here and seeing the parent comment first. Sounds like you can use WebSocket or any other transport mechanism.