Deprecating Comet?

[Rich Dougherty]

Hi Play people

Are many of you using Comet in your applications? It's been superseded for a while now by Server-Sent Events and WebSockets. I was idly wondering about whether we could deprecate Comet in a future version of Play. If Comet is still being used then we can maintain it pretty easily, but if no one's using it then we may as well deprecate it.

Here are the Comet docs for Play 2.4:

https://www.playframework.com/documentation/2.4.x/JavaComet

https://www.playframework.com/documentation/2.4.x/ScalaComet

Cheers

Rich

--

Rich Dougherty

Engineer, Typesafe, Inc

@richdougherty

[Manuel Bernhardt]

Hi,

I'm at the moment maintaining an application that has some Comet in it. I think one major reason for still using Comet is that SSE's are not supported by IE / Edge (see http://caniuse.com/#feat=eventsource) and that there are some network situations wherein WebSockets are blocked (e.g. some mobile network operators do block it, at least up until recently, as well as corporate firewalls sometimes get in the way as well).

I personally wouldn't mind too much for the application I'm maintaining because in that setting I could switch to WebSockets, however I think that not having Comet might hinder the adoption of Play in environments that can't use one of the alternatives.

Manuel

--
You received this message because you are subscribed to the Google Groups "Play framework dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framework-...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Rich Dougherty]

OK, thanks for the feedback! I didn't realise SSE isn't available in IE/ME.

[Rich Dougherty]

If anyone wants Microsoft Edge to support Server-Sent Events, you can vote for the feature here: https://wpdev.uservoice.com/forums/257854-project-spartan-platform/suggestions/6263825-server-sent-events-eventsource

– Rich

[Christopher Hunt]

> On 10 Feb 2016, at 7:24 AM, Rich Dougherty <ri...@rd.gen.nz> wrote:
>
> OK, thanks for the feedback! I didn't realise SSE isn't available in IE/ME.

I find it quite incredible that MS continues to hold the internet back.

[Naftoli Gugenheim]

How big is the maintenance burden / footprint of comet in Play? If it's not very big (or can be made smaller) then just because there are other means to a similar end isn't reason to delegate it. Only if it somehow is a threat of technical debt, then you have to weigh that against the rarity of the need for it.
Also, could it be made into a separate module?

--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framewor...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/play-framework/3F581762-7DB0-4E58-A753-F6093E5D4590%40typesafe.com.

[Rich Dougherty]

The ongoing maintenance burden for Comet is pretty low. I was asking because there is currently a task related to Comet that we need to complete for Play 2.5: https://github.com/playframework/playframework/issues/5602. If no one spoke up about using Comet then we could consider deprecating the API rather than doing the task. It would save a few hours. :)

– Rich

[Jun Yamog]

SSE is pretty much agreed comet, well IE does not agree. We used a polyfill for an internal SSE project. This can be an option for SSE, but we also added some heartbeat message on the play app.

https://github.com/Yaffle/EventSource

To view this discussion on the web visit https://groups.google.com/d/msgid/play-framework/CABW6spO%3DKXK9p7-C_3M8WTW-OL_AtRTB4y93%2B38ChZ-Attiu%3Dg%40mail.gmail.com.

[Loic]

Hi,

We are still using Comet in a critical Play frontend application so its availabilty is very important for us, as legacy browsers and IE don't support more modern APIs.
Anyway thanks a lot for asking :)

[Rich Dougherty]

On Sun, Feb 14, 2016 at 10:37 PM, Loic <loic.d...@gmail.com> wrote:

Anyway thanks a lot for asking :)

No worries!. Thanks for letting us know. :)