Lines Matching full:be
26 * An entity data can be read from and/or written to.
35 * If a transport is closed, it can be opened by calling open(), and vice
38 * While a transport should always be open when trying to read/write data,
43 * there is still data left to be read in the buffers. This choice has been
53 * A typical use case would be a server checking if it should process
81 * but waiting for new data to arrive would be required to fill the whole
82 * buffer, the readily available data will be immediately returned – use
107 * Must be called by clients when read is completed.
120 * and available to be read back in the future. Destroying a TTransport
122 * TTransport object with written but unflushed data, that data may be
133 * Must be called by clients when write is completed.
143 * Flushes any pending data to be written.
145 * Must be called before destruction to ensure writes are actually complete,
146 * otherwise pending data may be discarded. Typically used with buffered
162 * so protocols must be prepared to fall back to <code>read()</code> if
165 * The transport must be open when calling this.
168 * buf = A buffer where the data can be stored if needed, or null to
174 * null otherwise. The slice will be at least as long as requested, but
175 * may be longer if the returned slice points into an internal buffer
191 * The transport must be open when calling this.
278 * connections accepted from e.g. TServerSocket need to be wrapped into