Get desktop application:
View/edit binary Protocol Buffers messages
Returns the probs and normalization for given state.
errors: invalid state;
Returns the next state for symbol from context.
errors: none.
Next available ID: 2
Updates the count and normalization for given state and utf8_sym.
errors: invalid utf8_sym or count <= 0.
Next available ID: 4
State where count should be updated.
String of symbols whose count should be updated at that state.
Count to add to state and symbol.
Client authentication details: This message is supposed to be used in conjunction with the corresponding server authentication configuration defined in `ServerAuthConfig` message. Next available ID: 2
Used in:
TLS/TLS configuration for a secure gRPC channel. If not given, insecure connection is used.
Next available ID: 4
Used in:
Target name override for TLS host name checking. This should *not* be used in production. Normally, the name of the target should match the Common Name (aka `CN`) that represents the server name protected by the TLS certificate. The certificate is valid only if the request hostname matches the certificate common name. The Subject Alternative Name (SAN) is an extension to the X.509 specification that allows users to specify additional host names for a single TLS certificate. This is replacing Common Name (CN) mechanism. Example: See `subjectAltName` key in `opentls.conf` under the `testdata/x509` directory.
Public client certificate (PEM encoded).
Private client key for TLS (PEM encoded).
Next available ID: 9
Server configuration. Several values in server configuration, such as endpoint configuration and authentication details, are needed to in order to successfully establish client connections.
Client authentication details.
Type of request client will be making to the server.
Number of items to return in k_best extraction.
Context string prior to k_best extraction or random generation.
Test corpus for calculating bits-per-character.
Timeout when waiting for response from server specified in seconds.
Used in:
Client request type not set.
Returns k-best items following context_string.
Randomly generates string.
Calculates bits-per-char on given test_corpus.
Used in:
Not recommended for actual deployments when security and privacy are required.
https://en.wikipedia.org/wiki/Transport_Layer_Security
Next available ID: 3
Used as request type in: MozoLMService.GetLMScores, MozoLMService.GetNextState
Initial state for getting state information.
Context string (from initial state) for info.
Next available ID: 3
Used in:
Type of authorization credentials used in client/server handshake.
TLS/TLS configuration for a secure gRPC channel. If not given, insecure connection is used.
Configuration for TLS/SSL server credentials. This and the corresponding client-side configuration in `client_config.proto` introduces the following PEM-encoded credentials: - server_ca_cert: The certificate authority who has signed the `server_cert`. - server_cert: The server certificate chain, verified by the client via `server_ca_cert`. - server_key: The private key of the server. - client_ca_cert: The certificate authority who has signed the `client_cert`. - client_cert: The client certificate chain, verified by the server via `client_ca_cert`. - client_key: The private key of the client. The certificate authorities `server_ca_cert` and `client_ca_cert` may or may not be the same. For mutual authentication all of the above are required. Next available ID: 5
Used in:
Private server key for TLS (PEM encoded).
Public server certificate (PEM encoded).
Custom certificate authority (PEM encoded).
Whether a valid client certificate is required.
Next available ID: 6
Used in:
Model hub configuration.
The address to try to bind to the server in URI form. If the scheme name is omitted, "dns:///" is assumed. To bind to any address, please use IPv6 any, i.e., [::]:<port>, which also accepts IPv4 connections. Valid values include `dns:///localhost:1234`, `192.168.1.1:31416`, `dns:///[::1]:27182`, etc. To use UNIX domain, rather than TCP, sockets (aka UDS) use the "unix:///" scheme. Example: `unix:///tmp/example.sock`. Ideally the socket should be removed upon shutting down.
Configuration for authentication mechanisms.
Whether the server will wait for client requests. Always enabled by default, only disabled for the testing.
Number of threads for handling requests asynchronously.