Class ByteChannelContentSource
- All Implemented Interfaces:
Content.Source
- Direct Known Subclasses:
ByteChannelContentSource.PathContentSource
A Content.Source backed by a ByteChannel.
Any calls to demand(Runnable) are immediately satisfied.
-
Nested Class Summary
Nested Classes -
Constructor Summary
ConstructorsConstructorDescriptionByteChannelContentSource(ByteChannel byteChannel) ByteChannelContentSource(SeekableByteChannel seekableByteChannel, long offset, long length) ByteChannelContentSource(ByteBufferPool.Sized byteBufferPool, ByteChannel byteChannel) ByteChannelContentSource(ByteBufferPool.Sized byteBufferPool, SeekableByteChannel seekableByteChannel, long offset, long length) -
Method Summary
Modifier and TypeMethodDescriptionvoidDemands to invoke the given demand callback parameter when a chunk of content is available.voidFails this content source with alastfailure chunk, failing and discarding accumulated content chunks that were not yet read.longprotected voidlockedSetTerminal(Content.Chunk terminal) protected ByteChannelopen()read()Reads a chunk of content.booleanrewind()Rewinds this content, if possible, so that subsequent reads return chunks starting from the beginning of this content.Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface org.eclipse.jetty.io.Content.Source
fail
-
Constructor Details
-
ByteChannelContentSource
-
ByteChannelContentSource
public ByteChannelContentSource(ByteBufferPool.Sized byteBufferPool, SeekableByteChannel seekableByteChannel, long offset, long length) -
ByteChannelContentSource
-
ByteChannelContentSource
-
-
Method Details
-
open
- Throws:
IOException
-
demand
Description copied from interface:Content.SourceDemands to invoke the given demand callback parameter when a chunk of content is available.
See how to use this method idiomatically.
Implementations guarantee that calls to this method are safely reentrant so that stack overflows are avoided in the case of mutual recursion between the execution of the
Runnablecallback and a call to this method. Invocations of the passedRunnableare serialized and a callback fordemandcall is not invoked until any previousdemandcallback has returned. Thus theRunnableshould not block waiting for a callback of a future demand call.The demand callback may be invoked spuriously: a subsequent call to
Content.Source.read()may returnnull.Calling this method establishes a pending demand, which is fulfilled when the demand callback is invoked.
Calling this method when there is already a pending demand results in an
IllegalStateExceptionto be thrown.If the invocation of the demand callback throws an exception, then
Content.Source.fail(Throwable)is called.- Specified by:
demandin interfaceContent.Source- Parameters:
demandCallback- the demand callback to invoke where there is a content chunk available- See Also:
-
lockedSetTerminal
-
read
Description copied from interface:Content.SourceReads a chunk of content.
See how to use this method idiomatically.
The returned chunk could be:
null, to signal that there isn't a chunk of content available- an
Content.Chunkinstance with non nullContent.Chunk.getFailure(), to signal that there was a failure trying to produce a chunk of content, or that the content production has beenfailedexternally - a
Content.Chunkinstance, containing the chunk of content.
Once a read returns an
Content.Chunkinstance with non-nullContent.Chunk.getFailure()then if the failure islastfurther reads will continue to return the same failure chunk instance, otherwise furtherread()operations may return different non-failure chunks.Once a read returns a
last chunk, further reads will continue to return a last chunk (although the instance may be different).The content reader code must ultimately arrange for a call to
Retainable.release()on the returnedContent.Chunk.Additionally, prior to the ultimate call to
Retainable.release(), the reader code may make additional calls toRetainable.retain(), that must ultimately be matched by a correspondent number of calls toRetainable.release().Concurrent reads from different threads are not recommended, as they are inherently in a race condition.
Reads performed outside the invocation context of a
demand callbackare allowed. However, reads performed with a pending demand are inherently in a race condition (the thread that reads with the thread that invokes the demand callback).- Specified by:
readin interfaceContent.Source- Returns:
- a chunk of content, possibly a failure instance, or
null - See Also:
-
fail
Description copied from interface:Content.SourceFails this content source with a
lastfailure chunk, failing and discarding accumulated content chunks that were not yet read.The failure may be notified to the content reader at a later time, when the content reader reads a content chunk, via a
Content.Chunkinstance with a non nullContent.Chunk.getFailure().If
Content.Source.read()has returned a last chunk, this is a no operation.Typical failure: the content being aborted by user code, or idle timeouts.
If this method has already been called, then it is a no operation.
- Specified by:
failin interfaceContent.Source- Parameters:
failure- the cause of the failure- See Also:
-
getLength
public long getLength()- Specified by:
getLengthin interfaceContent.Source- Returns:
- the content length, if known, or -1 if the content length is unknown
-
rewind
public boolean rewind()Description copied from interface:Content.SourceRewinds this content, if possible, so that subsequent reads return chunks starting from the beginning of this content.
- Specified by:
rewindin interfaceContent.Source- Returns:
- true if this content has been rewound, false if this content cannot be rewound
-