good morning!!!!
Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
W
websocket
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Harbor Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
open
websocket
Commits
7196626d
Unverified
Commit
7196626d
authored
5 years ago
by
Anmol Sethi
Browse files
Options
Downloads
Patches
Plain Diff
More gentle comparison
I feel like this sentence was too much.
parent
dfda8a7d
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+0
-2
0 additions, 2 deletions
README.md
with
0 additions
and
2 deletions
README.md
+
0
−
2
View file @
7196626d
...
@@ -117,8 +117,6 @@ only 1400 lines whereas gorilla/websocket is at 3500 lines. That's more code to
...
@@ -117,8 +117,6 @@ only 1400 lines whereas gorilla/websocket is at 3500 lines. That's more code to
The future of gorilla/websocket is also uncertain. See
[
gorilla/websocket#370
](
https://github.com/gorilla/websocket/issues/370
)
.
The future of gorilla/websocket is also uncertain. See
[
gorilla/websocket#370
](
https://github.com/gorilla/websocket/issues/370
)
.
Pure conjecture but I would argue that the sprawling API has made it difficult to maintain.
Moreover, nhooyr/websocket has support for newer Go idioms such as context.Context and
Moreover, nhooyr/websocket has support for newer Go idioms such as context.Context and
also uses net/http's Client and ResponseWriter directly for WebSocket handshakes.
also uses net/http's Client and ResponseWriter directly for WebSocket handshakes.
gorilla/websocket writes its handshakes to the underlying net.Conn which means
gorilla/websocket writes its handshakes to the underlying net.Conn which means
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment