Support customization of supported keepalive count per transport
This change specifies the required minimum supported keepalives
in SDK, and allows OEMs to customize supported keepalive count
per network through resource overlay.
Bug: 129371366
Test: 1. m -j doc-comment-check-docs
2. atest FrameworksNetTests
Change-Id: I0218f3674628c13ead63fc9a873895ba7f113033
This commit is contained in:
parent
5218015ed8
commit
15e26fb485
1 changed files with 300 additions and 13 deletions
|
|
@ -43,6 +43,10 @@ import java.util.concurrent.Executor;
|
|||
* To stop an existing keepalive, call {@link SocketKeepalive#stop}. The system will call
|
||||
* {@link SocketKeepalive.Callback#onStopped} if the operation was successful or
|
||||
* {@link SocketKeepalive.Callback#onError} if an error occurred.
|
||||
*
|
||||
* The device SHOULD support keepalive offload. If it does not, it MUST reply with
|
||||
* {@link SocketKeepalive.Callback#onError} with {@code ERROR_UNSUPPORTED} to any keepalive offload
|
||||
* request. If it does, it MUST support at least 3 concurrent keepalive slots per transport.
|
||||
*/
|
||||
public abstract class SocketKeepalive implements AutoCloseable {
|
||||
static final String TAG = "SocketKeepalive";
|
||||
|
|
|
|||
Loading…
Reference in a new issue