Go to the latest version of this document.
search in docstrings

Search bar offers the following options:

- Term presence. The below example searches for documents that must contain “foo”, might contain “bar” and must not contain “baz”: `+foo bar -baz`
- Wildcards. The below example searches for documents with words beginning with “foo”: `foo*`
- Search in specific fields. The following search matches all objects in "twisted.mail" that matches “search”: `+qname:twisted.mail.* +search`

  Possible fields: 'name', 'qname' (fully qualified name), 'docstring', and 'kind'. Last two fields are only applicable if "search in docstrings" is enabled.

- Fuzzy matches. The following search matches all documents that have a word within 1 edit distance of “foo”: `foo~1`

Results provided by Lunr.js

# ``twisted`.`internet`.`ssl`.`ProtocolNegotiationSupport``

class documentation

`class ProtocolNegotiationSupport(Flags): (source)`

View In Hierarchy

`ProtocolNegotiationSupport` defines flags which are used to indicate the level of NPN/ALPN support provided by the TLS backend.

Constant | `ALPN` | The implementation supports Application Layer Protocol Negotiation.
Constant | `NPN` | The implementation supports Next Protocol Negotiation.
Class Variable | `NOSUPPORT` | There is no support for NPN or ALPN. This is exclusive with both `NPN` and `ALPN`.

ALPN = (source)

The implementation supports Application Layer Protocol Negotiation.

Value

    FlagConstant(2)

NPN = (source)

The implementation supports Next Protocol Negotiation.

Value

    FlagConstant(1)

NOSUPPORT = (source)

There is no support for NPN or ALPN. This is exclusive with both `NPN` and `ALPN`.