The max-pushes-per-session Element"
From Documentation
(2 intermediate revisions by one other user not shown) | |||
Line 5: | Line 5: | ||
[Default: -1] | [Default: -1] | ||
− | + | {{versionSince| 3.6.1}} | |
It specifies the maximum allowed number of concurrent server-push connections per session. | It specifies the maximum allowed number of concurrent server-push connections per session. | ||
Line 11: | Line 11: | ||
A negative number (default) means no limitation at all. Zero means no server push is allowed at all. | A negative number (default) means no limitation at all. Zero means no server push is allowed at all. | ||
− | Notices | + | Notices that |
* A desktop has at most one server-push connection. | * A desktop has at most one server-push connection. | ||
− | * A desktop might be killed accidentally. For example, | + | * A desktop might be killed accidentally. For example, a user closes a browser window. In this case, the server might not be able to detect it. When specifying this, it is better to specify the maximum allowed number of desktops. |
=Version History= | =Version History= |
Latest revision as of 04:24, 8 September 2023
Syntax:
<max-pushes-per-session>a_number</max-pushes-per-session>
[Default: -1]
Since 3.6.1
It specifies the maximum allowed number of concurrent server-push connections per session.
A negative number (default) means no limitation at all. Zero means no server push is allowed at all.
Notices that
- A desktop has at most one server-push connection.
- A desktop might be killed accidentally. For example, a user closes a browser window. In this case, the server might not be able to detect it. When specifying this, it is better to specify the maximum allowed number of desktops.
Version History
Version | Date | Content |
---|---|---|