Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update broken link in the [Introducing Socket.IO 1.0] blog section #460

Merged
merged 1 commit into from
Nov 21, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 10 additions & 10 deletions blog/2014-05-28-1.0.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,16 +14,16 @@ Socket.IO has thus become the `EventEmitter` of the web. Today I want to talk ab

There's a lot to say about Socket.IO 1.0, so if you're short in time, feel free to jump to the parts that are most interesting to you:

1. [New engine](#New-engine)
2. [Binary support](#Binary-support)
3. [Automated testing](#Automated-Testing)
4. [Scalability](#Scalability)
5. [Integration](#Integration)
6. [Better debugging](#Better-debugging)
7. [Streamlined APIs](#Streamlined-APIs)
8. [CDN delivery](#CDN-delivery)
9. [Future innovation](#Future-innovation)
10. [Credits](#Credits)
1. [New engine](#new-engine)
2. [Binary support](#binary-support)
3. [Automated testing](#automated-Testing)
4. [Scalability](#scalability)
5. [Integration](#integration)
6. [Better debugging](#better-debugging)
7. [Streamlined APIs](#streamlined-apis)
8. [CDN delivery](#cdn-delivery)
9. [Future innovation](#future-innovation)
10. [Credits](#credits)


## New engine
Expand Down