File tree Expand file tree Collapse file tree 3 files changed +15
-21
lines changed Expand file tree Collapse file tree 3 files changed +15
-21
lines changed Original file line number Diff line number Diff line change @@ -26,19 +26,17 @@ It is sometimes desirable for clients to receive a notification
26
26
when their connection gets [ blocked] ( ./alarms )
27
27
due to the broker running low on resources (memory or disk).
28
28
29
- We have introduced an AMQP 0-9-1 protocol extension in which the
30
- broker sends to the client a ` connection.blocked `
31
- method when the connection gets blocked, and ` connection.unblocked ` when it is unblocked.
29
+ A protocol extension to AMQP 0-9-1 has been introduced, enabling the broker to notify the client when
30
+ a connection is blocked or unblocked. The broker sends a ` connection.blocked ` method when the
31
+ connection is blocked, and a ` connection.unblocked ` method when it is unblocked.
32
32
33
33
To receive these notifications, the client must present a
34
34
` capabilities ` table in its ` client-properties ` in which there is a key
35
35
` connection.blocked ` and a boolean value ` true ` .
36
36
37
37
See the [ capabilities] ( ./connections#capabilities ) section for further
38
- details on this. Our supported clients indicate this capability
39
- by default and provide a way to register handlers for the
40
- ` connection.blocked ` and ` connection.unblocked ` methods.
41
-
38
+ details on this. Supported clients advertise this capability by default and provide mechanisms to register handlers
39
+ for the ` connection.blocked ` and ` connection.unblocked ` methods.
42
40
43
41
## When Notifications are Sent {#notifications}
44
42
Original file line number Diff line number Diff line change @@ -26,19 +26,17 @@ It is sometimes desirable for clients to receive a notification
26
26
when their connection gets [ blocked] ( ./alarms )
27
27
due to the broker running low on resources (memory or disk).
28
28
29
- We have introduced an AMQP 0-9-1 protocol extension in which the
30
- broker sends to the client a ` connection.blocked `
31
- method when the connection gets blocked, and ` connection.unblocked ` when it is unblocked.
29
+ A protocol extension to AMQP 0-9-1 has been introduced, enabling the broker to notify the client when
30
+ a connection is blocked or unblocked. The broker sends a ` connection.blocked ` method when the
31
+ connection is blocked, and a ` connection.unblocked ` method when it is unblocked.
32
32
33
33
To receive these notifications, the client must present a
34
34
` capabilities ` table in its ` client-properties ` in which there is a key
35
35
` connection.blocked ` and a boolean value ` true ` .
36
36
37
37
See the [ capabilities] ( ./connections#capabilities ) section for further
38
- details on this. Our supported clients indicate this capability
39
- by default and provide a way to register handlers for the
40
- ` connection.blocked ` and ` connection.unblocked ` methods.
41
-
38
+ details on this. Supported clients advertise this capability by default and provide mechanisms to register handlers
39
+ for the ` connection.blocked ` and ` connection.unblocked ` methods.
42
40
43
41
## When Notifications are Sent {#notifications}
44
42
Original file line number Diff line number Diff line change @@ -26,19 +26,17 @@ It is sometimes desirable for clients to receive a notification
26
26
when their connection gets [ blocked] ( ./alarms )
27
27
due to the broker running low on resources (memory or disk).
28
28
29
- We have introduced an AMQP 0-9-1 protocol extension in which the
30
- broker sends to the client a ` connection.blocked `
31
- method when the connection gets blocked, and ` connection.unblocked ` when it is unblocked.
29
+ A protocol extension to AMQP 0-9-1 has been introduced, enabling the broker to notify the client when
30
+ a connection is blocked or unblocked. The broker sends a ` connection.blocked ` method when the
31
+ connection is blocked, and a ` connection.unblocked ` method when it is unblocked.
32
32
33
33
To receive these notifications, the client must present a
34
34
` capabilities ` table in its ` client-properties ` in which there is a key
35
35
` connection.blocked ` and a boolean value ` true ` .
36
36
37
37
See the [ capabilities] ( ./connections#capabilities ) section for further
38
- details on this. Our supported clients indicate this capability
39
- by default and provide a way to register handlers for the
40
- ` connection.blocked ` and ` connection.unblocked ` methods.
41
-
38
+ details on this. Supported clients advertise this capability by default and provide mechanisms to register handlers
39
+ for the ` connection.blocked ` and ` connection.unblocked ` methods.
42
40
43
41
## When Notifications are Sent {#notifications}
44
42
You can’t perform that action at this time.
0 commit comments