Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

robscc / node-websocket-server Public

forked from nicokaiser/node-websocket-server

Notifications You must be signed in to change notification settings
Fork 0
Star 0

Code
Pull requests
Actions
Projects
Security
Insights

Additional navigation options

Code
Pull requests
Actions
Projects
Security
Insights

Breadcrumbs

node-websocket-server

/

problems.log

Copy path

Latest commit

History

2 lines (2 loc) · 218 Bytes

Breadcrumbs

node-websocket-server

/

problems.log

File metadata and controls

2 lines (2 loc) · 218 Bytes

1

2

1. if you send message too often(e.g send per 10ms), than unexpected thing will happen.Not sure whether it will happen if too many clients connected to the server (fixed 2011/9/25)

2. cannot handle frame fragmentation

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.