playframework / playframework/play-socket.io
Problems when sending client acks
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 96
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I recently timeboxed an exercise to try out play-socketio with a client callback. I attempted to modify the simple Chat sample app using the "Handling Acks" section of docs. I may be using the library wrong, or the client lib wrong, but what I observed is that the first event I emitted was ack'd properly in the client callback, but no subsequent event worked. I also expected the response I sent the callback to show up in the namespaced stream I setup, but I did not see it there.
These are the changes I made to the sample app:
https://github.com/playframework/play-socket.io/compare/master...seglo:master
https://github.com/seglo/play-socket.io/blob/master/samples/scala/chat/app/chat/ChatEngine.scala
Any assistance would be appreciated.
Thanks,
Sean
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
Read the "Handling Acks" section in docs/ScalaSocketIO.md and inspect the changes and sample file at samples/scala/chat/app/chat/ChatEngine.scala. Reproduce the Chat sample behavior using the linked comparison, then verify whether subsequent emitted events receive client callbacks and whether the callback response appears in the configured namespaced stream.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100