A stream that provides read-only stream functionality.
SDKs
- iOS 2.0+
- macOS 10.3+
- Mac Catalyst 13.0+
- tvOS 9.0+
- watchOS 2.0+
Framework
- Foundation
Declaration
@interface NSInputStream : NSStream
Overview
NSInput
is “toll-free bridged” with its Core Foundation counterpart, CFRead
. For more information on toll-free bridging, see Toll-Free Bridging.
Subclassing Notes
NSInput
is an abstract superclass of a class cluster consisting of concrete subclasses of NSStream
that provide standard read-only access to stream data. Although NSInput
is probably sufficient for most situations requiring access to stream data, you can create a subclass of NSInput
if you want more specialized behavior (for example, you want to record statistics on the data in a stream).
Methods to Override
To create a subclass of NSInput
you may have to implement initializers for the type of stream data supported and suitably re-implement existing initializers. You must also provide complete implementations of the following methods:
From the current read index, take up to the number of bytes specified in the second parameter from the stream and place them in the client-supplied buffer (first parameter). The buffer must be of the size specified by the second parameter. Return the actual number of bytes placed in the buffer; if there is nothing left in the stream, return
0
. Reset the index into the stream for the next read operation.Return in 0(1) a pointer to the subclass-allocated buffer (first parameter). Return by reference in the second parameter the number of bytes actually put into the buffer. The buffer’s contents are valid only until the next stream operation. Return
NO
if you cannot access data in the buffer; otherwise, returnYES
. If this method is not appropriate for your type of stream, you may returnNO
.Return
YES
if there is more data to read in the stream,NO
if there is not. If you want to be semantically compatible withNSInput
, returnStream YES
if a read must be attempted to determine if bytes are available.