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”:
Search in specific fields. The following search matches all objects
in "twisted.mail" that matches “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”:
Results provided by Lunr.js
_BypassTLS is used as the transport object for the TLS protocol object used to implement startTLS. Its methods skip any TLS logic which startTLS enables.
||Forward any extra attribute access to the original transport object. For example, this exposes getHost, the behavior of which does not change after TLS is enabled.|
||Close the underlying connection.|
||Register a producer with the underlying connection.|
||Unregister a producer with the underlying connection.|
||Write some bytes directly to the connection.|
||Write a some bytes directly to the connection.|
||A transport class
Forward any extra attribute access to the original transport object. For example, this exposes getHost, the behavior of which does not change after TLS is enabled.
Register a producer with the underlying connection.
A transport class
_BypassTLS has been mixed in with to which methods will be forwarded. This class is only responsible for sending bytes over the connection, not doing TLS.
Connection which TLS has been started on which will be proxied to by this object. Any method which has its behavior altered after startTLS will be skipped in favor of the base class's implementation. This allows the TLS protocol object to have direct access to the transport, necessary to actually implement TLS.