Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Deprecate Atmosphere #1083

Closed
magnolia-k opened this issue Dec 30, 2020 · 2 comments
Closed

Deprecate Atmosphere #1083

magnolia-k opened this issue Dec 30, 2020 · 2 comments
Milestone
2.8.0

Comments

@magnolia-k
Copy link
Contributor

The Atmosphere is currently not very actively maintained.

And Atmosphere is the most significant obstacle to making Scalatra compatible with the latest Servlet APIs.

Also, Atmosphere supports a variety of middleware and protocols, which makes it too complex to simply use WebSockets.

We could introduce a simpler WebSocket mechanism (e.g. a simple wrapper for the functionality provided by Jetty) and stop supporting Atmosphere.
@magnolia-k magnolia-k added this to the 2.8.0 milestone Dec 30, 2020
@takezoe takezoe closed this as completed Jul 25, 2021
@dlnorgaard
Copy link

dlnorgaard commented Nov 2, 2022 •
edited

@takezoe Hi. Just wanted to confirm the plans for this. I am not seeing org.scalatra.atmosphere.AtmosphereClient being marked deprecated in 2.8.4.

@takezoe
Copy link
Member

takezoe commented Nov 3, 2022 •
edited

@dlnorgaard AtmosphereSupport which is required to use Atmosphere integration in Scalatra has been marked as deprecated: 0f7d788

The status is the same as Scalate integration. It will be maintained in Scalatra 2.8.x and dropped in Scalatra 3.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.8.0
Development

No branches or pull requests
3 participants
@takezoe @magnolia-k @dlnorgaard