6 Commits

Include renames

Author	SHA1	Message	Date
Rob Austin	ef0cd0f96f	HCOLL-155 removed acquireUsingReadLocked and acquireUsingWriteLocked to WriteContext<K,V> acquireUsingLocked(@NotNull K key, @NotNull V usingValue); and ReadContext<K,V> getUsingLocked(@NotNull K key, @NotNull V usingValue);	2014-11-02 18:35:26 +00:00
Rob Austin	118ed1676f	HCOLL-155 added two of peters tests and them implemented the code accordingly - the test are net.openhft.chronicle.map.ChronicleMapTest#testOffheapAcquireUsingLocked and net.openhft.chronicle.map.ChronicleMapTest#testOnheapAcquireUsingLocked	2014-11-02 00:16:02 +00:00
Rob Austin	100d839a8b	HCOLL-155 uncompleted, checked in order that Peter can review the changes so far of - chm.acquireUsingReadLocked and chm.acquireUsingWriteLocked	2014-11-01 15:53:47 +00:00
leventov	0c45ee8aff	HCOLL-136 HCOLL-137 HCOLL-153 HCOLL-160 ... 1. Separated ChronicleMapBuilder (for non-Byteable values) and OffHeapUpdatableChronicleMapBuilder (for Byteable values) with common base AbstractChronicleMapBuilder (public just to inherit common javadocs) 2. Added ChronicleHashBuilder.keyDeserializationFactory() and AbstractChronicleMapBuilder.valueDeserializationFactory() (former ChronicleMapBuilder.valueFactory() method) 3. Changed ChronicleMap.get(), getUsing() API and impl to what was initially intended - now they ALWAYS returns null, if key is absent 4. acquireUsing() API, common for the cases with Byteable and non-Byteable values: puts defaultValue or defaultValueProvider.get(key), if the key is absent, then acquireUsing() behaves just like getUsing() 5. For off0heap updatable ChronicleMaps (Byteable values), added prepareValueBytes() configuration which formalizes zeroing out value bytes 6. Javadoc fixes and improvements	2014-10-27 20:15:26 +03:00
Peter Lawrey	ea779997cf	Remove <p/> from copyright messages	2014-10-24 11:30:25 +01:00
leventov	ea16356d46	New Chronicle-Map	2014-09-05 17:39:51 +04:00