Alawn/Chronicle-Map
1
0
Fork 0
mirror of https://github.com/OpenHFT/Chronicle-Map.git synced 2021-09-13 01:26:12 +00:00
Code Releases Activity

changed the wording arround -

Browse Source 
``` java
                              .of(CharSequence.class, DataValueClasses.directClassFor(BondVOInterface.class))
                              ```
This commit is contained in:
Rob Austin
2014-12-21 09:13:37 +00:00
parent f5a2b83469
commit 3ab0e6d86f
1 changed files with 7 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+7 -8
View File
@@ -461,8 +461,9 @@ lets say that it is only the `coupon` field that we are interested in, then its
deserialise the whole object that implements the `BondVOInterface`. The `ChronicleMapBuilder` will look a the types of keys
and values that you use, If the value type is a simple accessor/mutator interface that is exposing a non nested pojo, which uses simple types
like `CharSequence` and primitives with corresponding get..() and
set..() methods, Chronicle is able to generate off heap poxies so the whole object is not desrialized each
time it is accessed, The off heap poxies are able to read
set..() methods, Chronicle is able to generate off heap poxies so the whole object is not
deserialized each
time it is accessed, The off heap proxies are able to read
and write into
the off heap data structures directly, this reduced serialisation can give you a big performance boost.
Below we show you how you can work directly with the off heap entries.
@@ -474,18 +475,16 @@ ChronicleMap<CharSequence, BondVOInterface> map = ChronicleMapBuilder
.create();
```
notice that the
notice that the the builder is passed a wrapped value type
``` java
.of(CharSequence.class, DataValueClasses.directClassFor(BondVOInterface.class))
```
we have to wrap the interface ( in this example the BondVOInterface ), with DataValueClasses
.directClassFor(...) method, in
order
to tell the builder that we are going to work directly with the off heap entries.
this is order to tell the builder that we are going to work directly with the off heap
entries.
value class, in our case `BondVOInterface.class` is an `interface` rather than a `class`, now
The value class, in our case `BondVOInterface.class` is an `interface` rather than a `class`, now
like before, we can
use the `getUsing(key,using)` method, but this time we have to create the ‘using’ instance slightly
differently, we have to call either the `map.newValueInstance()` or `map.newKeyInstance()` method.