Package ome.io.nio

New Input/Output handling for the OMERO server This includes interfaces/classes for the input and output handling of data within the OMERO server.

See: Description

Interface Summary

Interface	Description
BackOff	Strategy interface which is used by PixelsService to calculate the appropriate backoff to report to users when pixel data is not available.
FilePathResolver	Resolver for file paths and related metadata.
PixelBuffer	This interface declares the I/O responsibilities of a buffer, file or otherwise, that contains a 5-dimensional Pixel array (XYZCT).
TileLoopIteration	A single iteration of a tile for each loop.
TileSizes	Strategy interface which is used by PixelsService to specify the default tile sizes as well as when tiling is necessary.

Class Summary

Class	Description
AbstractBuffer
AbstractFileSystemService
ConfiguredTileSizes	Implementation which has all values injected during configuration.
FileBuffer	Raw file buffer which provides I/O operations within the OMERO file repository.
InMemoryPlanarPixelBuffer	Class implementation of the PixelBuffer interface for in memory planar pixel data.
OriginalFilesService	Raw file service which provides access to FileBuffers.
PixelsService
ReorderedPixelData	Represents a block of pixel data that needs to be re-ordered in accordance with a DeltaVision file.
RomioPixelBuffer	Class implementation of the PixelBuffer interface for standard "proprietary" ROMIO/OMEIS data format.
SimpleBackOff	Basic BackOff implementation which attempts several writes of the default block size on startup, and uses that as a scaling factor for all subsequent calculations.
ThumbnailService
Utils	General utility methods for working with ROMIO classes.

Exception Summary

Exception	Description
DimensionsOutOfBoundsException
PixelBufferException
Utils.FailedTileLoopException	The processing of a tile failed so abort the loop.

Package ome.io.nio Description

New Input/Output handling for the OMERO server

This includes interfaces/classes for the input and output handling of data within the OMERO server.

Related Documentation

For more information, please see:

• TODO