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
A cache is a local representation of a remote
This represents the last known state of this object. It may also have methods invoked on it -- in order to update caches, the cached class generates a
pb.RemoteReference to this object as it is originally sent.
Much like copy, I will be invoked with no arguments. Do not implement a constructor that requires arguments in one of my subclasses.
||Compare me [to another RemoteCache.|
||Do distributed reference counting on finalize.|
||serialize me (only for the broker I'm for) as the original cached reference|
||A remote message has been received. Dispatch it appropriately.|
||Perform the inverse operation of
||Create a new object that shares its state (i.e. its __dict__) and type with this object, but does not share its identity.|
||I will be invoked with the state to copy locally.|
||Return an ID which uniquely represents this object for this process.|
A remote message has been received. Dispatch it appropriately.
The default implementation is to dispatch to a method called 'observe_messagename' and call it on my with the same arguments.
Create a new object that shares its state (i.e. its __dict__) and type with this object, but does not share its identity.
This is an instance of the Borg design pattern originally described by Alex Martelli, but unlike the example given there, this is not a replacement for a Singleton. Instead, it is for lifecycle tracking (and distributed garbage collection). The purpose of these separate objects is to have a separate object tracking each application-level reference to the root
RemoteCache object being tracked by the broker, and to have their __del__ methods be invoked.
This may be achievable via a weak value dictionary to track the root
RemoteCache instances instead, but this implementation strategy predates the availability of weak references in Python.
|self.__class__||The new instance.|