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`.`interfaces`.`IUNIXTransport``

interface documentation

`class IUNIXTransport(ITransport): (source)`

Known implementations: `twisted.internet.unix.Client`, `twisted.internet.unix.Server`

View In Hierarchy

Transport for stream-oriented unix domain connections.

Method | `sendFileDescriptor` | Send a duplicate of this (file, socket, pipe, etc) descriptor to the other end of this connection.

Inherited from `ITransport`:

Method | `getHost` | Similar to getPeer, but returns an address describing this side of the connection.
Method | `getPeer` | Get the remote address of this connection.
Method | `loseConnection` | Close my connection, after writing all pending data.
Method | `write` | Write some data to the physical connection, in sequence, in a non-blocking fashion.
Method | `writeSequence` | Write an iterable of byte strings to the physical connection.

def sendFileDescriptor(descriptor: `int`): (source)

Send a duplicate of this (file, socket, pipe, etc) descriptor to the other end of this connection.

The send is non-blocking and will be queued if it cannot be performed immediately. The send will be processed in order with respect to other `sendFileDescriptor` calls on this transport, but not necessarily with respect to `write` calls on this transport. The send can only be processed if there are also bytes in the normal connection-oriented send buffer (ie, you must call `write` at least as many times as you call `sendFileDescriptor`).

Parameters
descriptor:`int` | An `int` giving a valid file descriptor in this process. Note that a file descriptor may actually refer to a socket, a pipe, or anything else POSIX tries to treat in the same way as a file.