Uses of Package
one.microstream.memory
| Package | Description |
|---|---|
| one.microstream.memory | |
| one.microstream.memory.android | |
| one.microstream.memory.sun |
-
Classes in one.microstream.memory used by one.microstream.memory Class Description DirectBufferDeallocator The combination of: Missing proper DirectByteBuffer public API interface type, Missing deallocate() possibility for direct ByteBuffers, sun.misc.Cleaner package change with Java 9, modules with Java 9 AND java.base not exporting its stuff so that halfway proper workarounds for the JDK design errors could be created using reflection without forcing special vm arguments on everyone wanting to use the library leave only one sanity-preserving way to handle explicit deallocation of memory directly allocated byByteBuffer.allocateDirect(int):MemoryAccessor MemoryAccessorGeneric MemorySizeProperties MemoryStatistics MemoryStatisticsProvider -
Classes in one.microstream.memory used by one.microstream.memory.android Class Description DirectBufferDeallocator The combination of: Missing proper DirectByteBuffer public API interface type, Missing deallocate() possibility for direct ByteBuffers, sun.misc.Cleaner package change with Java 9, modules with Java 9 AND java.base not exporting its stuff so that halfway proper workarounds for the JDK design errors could be created using reflection without forcing special vm arguments on everyone wanting to use the library leave only one sanity-preserving way to handle explicit deallocation of memory directly allocated byByteBuffer.allocateDirect(int): -
Classes in one.microstream.memory used by one.microstream.memory.sun Class Description DirectBufferAddressGetter Similar toDirectBufferDeallocatorbut to obtain the DirectBuffer's address value.DirectBufferDeallocator The combination of: Missing proper DirectByteBuffer public API interface type, Missing deallocate() possibility for direct ByteBuffers, sun.misc.Cleaner package change with Java 9, modules with Java 9 AND java.base not exporting its stuff so that halfway proper workarounds for the JDK design errors could be created using reflection without forcing special vm arguments on everyone wanting to use the library leave only one sanity-preserving way to handle explicit deallocation of memory directly allocated byByteBuffer.allocateDirect(int):MemoryAccessor MemorySizeProperties