Stream module containing stream utility methods.
This module provides a set of methods for interacting with
IOStream objects, including asynchronous versions of the
read and write methods offered by all stream objects. These
methods should be used in any place where reading from or writing
to a stream might block.
See also:
The following example shows how to use the pump method.
var pumpCallback = function(arg) {
if(arg.bytesProcessed == -1) {
Ti.API.info("At end of stream.");
} else {
Ti.API.info(String.format("Received %.0f bytes. Total: %.0f bytes.",
arg.bytesProcessed, arg.totalBytesProcessed));
// do something useful with the data in arg.buffer
}
}
Ti.Stream.pump(inputStream, pumpCallback, 1024);
The following example uses the writeStream method
to copy the contents of an input stream to a file. This can be used for any kind
of input stream -- BufferStream, FileStream, or Socket.TCP.
var outFileStream = Ti.Filesystem.getFile('outfile.txt').open(Ti.Filesystem.MODE_WRITE);
// writes all data from inputStream to outFileStream in chunks of 1024 bytes
var bytesWritten = Ti.Stream.writeStream(inputStream, outFileStream, 1024);
Ti.API.info('Wrote ' + bytesWritten + ' bytes, closing both streams.');
inputStream.close();
outFileStream.close();
Use with createStream to open a stream in append mode.
Use with createStream to open a stream in append mode.
Use with createStream to open a stream in read mode.
Use with createStream to open a stream in read mode.
Use with createStream to open a stream in write mode.
Use with createStream to open a stream in write mode.
The name of the API that this proxy corresponds to.
The name of the API that this proxy corresponds to.
The value of this property is the fully qualified name of the API. For example, Button
returns Ti.UI.Button.
Indicates if the proxy will bubble an event to its parent.
Some proxies (most commonly views) have a relationship to other proxies, often established by the add() method. For example, for a button added to a window, a click event on the button would bubble up to the window. Other common parents are table sections to their rows, table views to their sections, and scrollable views to their views. Set this property to false to disable the bubbling to the proxy's parent.
Default: true
The Window or TabGroup whose Activity lifecycle should be triggered on the proxy.
The Window or TabGroup whose Activity lifecycle should be triggered on the proxy.
If this property is set to a Window or TabGroup, then the corresponding Activity lifecycle event callbacks will also be called on the proxy. Proxies that require the activity lifecycle will need this property set to the appropriate containing Window or TabGroup.
Adds the specified callback as an event listener for the named event.
Name of the event.
Callback function to invoke when the event is fired.
Applies the properties to the proxy.
Properties are supplied as a dictionary. Each key-value pair in the object is applied to the proxy such that myproxy[key] = value.
A dictionary of properties to apply.
Creates stream from a Buffer or Blob object.
Returns Titanium.BufferStream or Titanium.BlobStream depending on whether a
Buffer or Blob is provided as the source property in params.
Blob obects are read only. Throws an exception if MODE_WRITE or MODE_APPEND is
specified along with a blob object.
Parameter object, for specifying the source object and mode.
Fires a synthesized event to any registered listeners.
Name of the event.
A dictionary of keys and values to add to the Titanium.Event object sent to the listeners.
Reads data from input stream and passes it to a handler method.
After the end of the input stream is reached, the handler is called
a final time with no data and bytesProcessed set to -1 to indicate
the end of the input data.
Stream to pump from.
Handler method that will receive data from inputStream.
Maximum number of bytes to pass to handler in a single call.
Specifies if the pump operation should run asynchronously.
Asynchronously reads data from an IOStream into a buffer.
Reads data from the stream and writes it to the buffer. The first byte is
written to buffer[offset]. Reads until the provided buffer is full, the end of
the stream is detected, or the requested number of bytes have been read. Does not
resize the supplied buffer.
A request must include both offset and length parameters, or omit them both.
If the stream is not readable, an error is reported:
On iOS, throws an exception.
On Android, calls the callback with an error.
If offset is past the last byte of the buffer, throws an exception.
Stream to read from.
Buffer to read into.
Offset to start reading stream data from, in bytes.
If specified, length must be specified as well.
Number of bytes of data to read from the stream.
If specified, offset must be specified as well.
Function to call with the results of the read operation.
Reads all data from the specified IOStream.
Reads data from the stream, either synchronously or asynchronously.
Throws an exception if a read error is encountered or data can't be written to the buffer.
If the optional buffer and resultsCallback arguments are specified, the read operation
takes place asynchronously, and the results are passed to the callback.
The data is written to the provided buffer, which is resized if necessary.
If the buffer and resultsCallback arguments are omitted, a new buffer is
allocated and returned.
Stream to read from.
Buffer to read into. If specified, resultsCallback must be specified as
well.
Function to call with the results of the read operation.
If specified, resultsCallback must be specified as well.
Removes the specified callback as an event listener for the named event.
Multiple listeners can be registered for the same event, so the
callback parameter is used to determine which listener to remove.
When adding a listener, you must save a reference to the callback function in order to remove the listener later:
var listener = function() { Ti.API.info("Event listener called."); }
window.addEventListener('click', listener);
To remove the listener, pass in a reference to the callback function:
window.removeEventListener('click', listener);
Name of the event.
Callback function to remove. Must be the same function passed to addEventListener.
Sets the value of the bubbleParent property.
New value for the property.
Sets the value of the lifecycleContainer property.
New value for the property.
Asynchronously writes data from a buffer to an IOStream.
Data is read from the buffer and written to the stream.
If the offset and length arguments are specified, data is read from the buffer
starting at offset, up to offset+length-1 or the end of the buffer, whichever
comes first.
If offset and length are omitted, the entire buffer is written to the stream.
If the output stream is not writable, an error is reported:
On iOS, an exception is thrown.
On Android, the callback is invoked with an error.
Stream to write to.
Buffer to write from.
Offset to start writing buffer data from.
If specified, length must be specified as well.
Bytes of data to write. If specified, offset must be specified as well.
Function to call with the results of the write operation.
Writes all data from an input stream to an output stream.
If the optional resultsCallback argument is supplied, the operation is
performed asynchronously.
If the callback is omitted, this method is synchronous, and blocks until all data has been written.
The synchronous version Returns the total number of bytes written.
If no data can be read from the input stream because the input stream is at end of stream, behavior varies by platform:
iOS throws an exception.
Android returns 0, or calls the callback with bytesProcessed set to 0.
Stream to read from.
Stream to write to.
Maximum number of bytes to copy from inputStream to outputStream in a
single operation.
Function to call with the results of the writeStream operation.