7 Commits

Include renames

Author	SHA1	Message	Date
leventov	4a51b129a3	Many renames, API refactorings, classes/interfaces made private to net.openhft.chronicle.map package ... Conflicts: src/main/java/net/openhft/chronicle/map/StatelessChronicleMap.java src/test/java/net/openhft/chronicle/map/ChronicleMapTest.java	2014-11-07 12:10:40 +03:00
Rob Austin	9dec1ed4db	reverted cff7c5bea8	2014-11-04 14:44:59 +00:00
Rob Austin	a0c89935f5	reverted cff7c5bea8	2014-11-04 14:29:06 +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
Rob Austin	8e57eeafc2	HCOLL-167 simplified the map builder by making "file" very much an option parameter, is it not REQUIRED for all types of maps. Also updated the many of the TCP replication test to remove the user of file() as its simply not required for this in many cases.	2014-10-20 17:19:27 +01:00
leventov	ea16356d46	New Chronicle-Map	2014-09-05 17:39:51 +04:00