Results for: "match"

spell checker for a dictionary that has a tree structure, see doc/tree_spell_checker_api.md

Error raised by a dRuby protocol when it doesn’t support the scheme specified in a URI. See DRb::DRbProtocol.

The default drb protocol which communicates over a TCP socket.

The DRb TCP protocol URI looks like: druby://<host>:<port>?<option>. The option is optional.

No documentation available
No documentation available
No documentation available

Response class for Created responses (status code 201).

The Created response indicates that the server has received and has fulfilled a request to create a new resource. See 201 Created.

Response class for Reset Content responses (status code 205).

The Reset Content response indicates that the server successfully processed the request, asks that the client reset its document view, and is not returning any content. See 205 Reset Content.

Response class for Multi-Status (WebDAV) responses (status code 207).

The Multi-Status (WebDAV) response indicates that the server has received the request, and that the message body can contain a number of separate response codes. See 207 Multi-Status (WebDAV).

Response class for Multiple Choices responses (status code 300).

The Multiple Choices response indicates that the server offers multiple options for the resource from which the client may choose. See 300 Multiple Choices.

Response class for Multiple Choices responses (status code 300).

The Multiple Choices response indicates that the server offers multiple options for the resource from which the client may choose. See 300 Multiple Choices.

Response class for Moved Permanently responses (status code 301).

The Moved Permanently response indicates that links or records returning this response should be updated to use the given URL. See 301 Moved Permanently.

Response class for Permanent Redirect responses (status code 308).

This and all future requests should be directed to the given URI. See 308 Permanent Redirect.

Response class for Proxy Authentication Required responses (status code 407).

The client must first authenticate itself with the proxy. See 407 Proxy Authentication Required.

Response class for Unsupported Media Type responses (status code 415).

The request entity has a media type which the server or resource does not support. See 415 Unsupported Media Type.

Response class for Range Not Satisfiable responses (status code 416).

The request entity has a media type which the server or resource does not support. See 416 Range Not Satisfiable.

Response class for Range Not Satisfiable responses (status code 416).

The request entity has a media type which the server or resource does not support. See 416 Range Not Satisfiable.

Response class for Expectation Failed responses (status code 417).

The server cannot meet the requirements of the Expect request-header field. See 417 Expectation Failed.

Response class for Too Many Requests responses (status code 429).

The user has sent too many requests in a given amount of time. See 429 Too Many Requests.

Response class for Bad Gateway responses (status code 502).

The server was acting as a gateway or proxy and received an invalid response from the upstream server. See 502 Bad Gateway.

Response class for Gateway Timeout responses (status code 504).

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server. See 504 Gateway Timeout.

Response class for Gateway Timeout responses (status code 504).

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server. See 504 Gateway Timeout.

Response class for Variant Also Negotiates responses (status code 506).

Transparent content negotiation for the request results in a circular reference. See 506 Variant Also Negotiates.

Response class for Network Authentication Required responses (status code 511).

The client needs to authenticate to gain network access. See 511 Network Authentication Required.

No documentation available
Search took: 4ms  ·  Total Results: 1861