From 488a2fe4a7cb8c2fe01e4e591ffaf45245f870ad Mon Sep 17 00:00:00 2001 From: Rob Austin Date: Mon, 17 Nov 2014 11:19:35 +0000 Subject: [PATCH] updated the readme to reflect the new simple single builder --- README.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 88cac1466..c96a7625e 100644 --- a/README.md +++ b/README.md @@ -426,8 +426,12 @@ bond.getCoupon() ``` lets say that it is only the `coupon` field that we are interested in, then its better not to have to -deserialize the whole object that implements the `BondVOInterface`. It would be more efficient to just -deserialize the field(s) that we require, in this example just the coupon. This is why we created +deserialize the whole object that implements the `BondVOInterface`. Chronicle will look a the types of keys + and values that you set up in the builder, If the value type is a simple accessor/mutator interfaces + inother words a simple interface that is exposing non nested pojo with coresonding getX() and setX() + methods Chronicle is able to be act in a more efficient way, by just deserialize the field(s) that we + require, in this + example just the coupon. This is why we created the`ChronicleMapBuilder`, when you use this builder chronicle will not create on heap copies of your whole data structure. You can instead use proxy objects that can read and write into the off heap data structures, this reduced serialisation can give you a big performance boost. Below we show you how you can work directly with the off heap entries. ``` java