Lift 5: Web Sockets
Open
Nobody has claimed this yet.
Lift5
- Dominant language
- Scala
- Stars
- 1.3k
- Forks
- 275
- PR merge metrics
- No merged PRs in 30d
Description
https://groups.google.com/g/liftweb/c/sG2HWm4I3g0/m/lYvrejBkCAAJ?utm_medium=email&utm_source=footer
Use Web Sockets rather than long polling for Comet Actors and other stuff (delayed rendering, browser/server actors, etc.) if Web Sockets are available.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked Google Groups discussion and the issue's references to Comet Actors, delayed rendering, and browser/server actors. Determine the scope and design for preferring WebSockets when available while preserving behavior when they are not; done means the affected real-time features use that transport appropriately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100