Insert explicit ids for headers
This commit is contained in:
@@ -1,4 +1,5 @@
|
||||
[id={chapter}.websocket-intro]
|
||||
[[introduction-to-websocket]]
|
||||
= Introduction to WebSocket
|
||||
|
||||
The WebSocket protocol, https://tools.ietf.org/html/rfc6455[RFC 6455], provides a standardized
|
||||
@@ -55,6 +56,7 @@ instructions of the cloud provider related to WebSocket support.
|
||||
|
||||
|
||||
[id={chapter}.websocket-intro-architecture]
|
||||
[[http-versus-websocket]]
|
||||
== HTTP Versus WebSocket
|
||||
|
||||
Even though WebSocket is designed to be HTTP-compatible and starts with an HTTP request,
|
||||
@@ -81,6 +83,7 @@ In the absence of that, they need to come up with their own conventions.
|
||||
|
||||
|
||||
[id={chapter}.websocket-intro-when-to-use]
|
||||
[[when-to-use-websockets]]
|
||||
== When to Use WebSockets
|
||||
|
||||
WebSockets can make a web page be dynamic and interactive. However, in many cases,
|
||||
|
||||
Reference in New Issue
Block a user