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
class AccumulatingProtocol(protocol.Protocol): (source)
AccumulatingProtocol is an
IProtocol implementation which collects the data delivered to it and can fire a Deferred when it is connected or disconnected.
||Called when the connection is shut down.|
||Called when a connection is made.|
||Called whenever data is received.|
||A flag indicated whether connectionLost has been called.|
||If set to a
||The value of the reason parameter passed to connectionLost.|
||Bytes giving all the data passed to dataReceived.|
||A flag indicating whether connectionMade has been called.|
||Return a prefix matching the class name, to identify log messages related to this protocol instance.|
||Make a connection to a transport and a server.|
Called when the connection is shut down.
Clear any circular references here, and any external references to this Protocol. The connection has been closed.
Called when a connection is made.
This may be considered the initializer of the protocol, because it is called when the connection is completed. For clients, this is called once the connection to the server has been established; for servers, this is called after an accept() call stops blocking and a socket has been received. If you need to send any greeting or initial message, do it here.
Called whenever data is received.
Use this method to translate to a higher-level message. Usually, some callback will be made upon the receipt of each complete protocol message.
|data||a string of indeterminate length. Please keep in mind that you will probably need to buffer some data, as partial (or multiple) protocol messages may be received! I recommend that unit tests for protocols call through to this method with differing chunk sizes, down to one byte at a time.|