share / share/sharedb

How do I implement custom messages, just like websockets

Open
#633 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
6.5k
Forks
456
Avg merge
1d 5h
Merged PRs (30d)
5

Description

I have a requirement that the client only sends data to the server, and the server can freely choose who to push messages to, just like a native websocket. The purpose of doing so is to send authentication information to the server, and the server can return the permissions I have, such as read-only. I know this can be achieved using websocket, but I hope to directly access agent.custom during the authentication process and bind the permission information to it.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the authentication process and the references to agent.custom in the issue, then compare the requested behavior with native websocket message routing. Confirm whether the project has an existing entry point for server-directed custom messages and permission data; the issue is complete only when the intended behavior and its scope are clearly defined.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
authentication, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.