@@ -462,7 +462,7 @@ When sending blocking requests, the WebSocket connection shall not be closed by
...
@@ -462,7 +462,7 @@ When sending blocking requests, the WebSocket connection shall not be closed by
When sending non-blocking requests, the WebSocket connection shall not be closed by the registrar before the acknowledgment response is received, or before any configured timeout period has expired. If the entities' communication policies and power saving requirements allow, the connection should be kept open at least until an ongoing procedure has fully completed, i.e. requesting of the result in synchronous mode or completion of Notify procedure in asynchronous mode.
When sending non-blocking requests, the WebSocket connection shall not be closed by the registrar before the acknowledgment response is received, or before any configured timeout period has expired. If the entities' communication policies and power saving requirements allow, the connection should be kept open at least until an ongoing procedure has fully completed, i.e. requesting of the result in synchronous mode or completion of Notify procedure in asynchronous mode.
If no associated WebSocket connection between a registree and a registrar exists when a request primitive for this registree becomes available at the registrar's side and the procedure for a *request reachable* target do not apply, then the procedure described in TS-0004 [TODO], clause 7.3.3.9.1, shall be followed with the following additions:
If no associated WebSocket connection between a registree and a registrar exists when a request primitive for this registree becomes available at the registrar's side and the procedure for a *request reachable* target do apply, then the procedure described in TS-0004 [TODO], clause 7.3.3.9.1, shall be followed with the following additions:
- If the processed *pointOfAccess* address is a WebSocket URL with the value *ws://default* and there is an established WebSocket connection between the registree and the registrar, then the registrar will handle the request and response via the established WebSocket connection. If there is no established WebSocket connection, then this URI is skipped and the iteration of the *pointOfAccess* attribute continues.
- If the processed *pointOfAccess* address is a WebSocket URL with the value *ws://default* and there is an established WebSocket connection between the registree and the registrar, then the registrar will handle the request and response via the established WebSocket connection. If there is no established WebSocket connection, then this URI is skipped and the iteration of the *pointOfAccess* attribute continues.
- If the process *pointOfAccess* address is a WebSocket URL other than the value *ws://default* then the registrar establishes a new WebSocket connection with the WebSocket server at that URL, if not already established, and, on success, handles the request and response via this WebSocket connection. After this the registrar may close the WebSocket connection.
- If the process *pointOfAccess* address is a WebSocket URL other than the value *ws://default* then the registrar establishes a new WebSocket connection with the WebSocket server at that URL, if not already established, and, on success, handles the request and response via this WebSocket connection. After this the registrar may close the WebSocket connection.