You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Coherence JavaScript Client allows Node applications to act as
11
-
cache clients to a Coherence Cluster using gRPC framework as
11
+
cache clients to a Coherence Cluster using Google's gRPC framework for
12
12
the network transport.
13
13
14
14
### Features
@@ -18,16 +18,16 @@ the network transport.
18
18
* Registration of listeners to be notified of map mutations
19
19
20
20
### Requirements
21
-
* Coherence CE 20.12 or later (or equivalent non-open source editions) with a configured [gRPC Proxy](https://github.com/oracle/coherence/tree/master/prj/coherence-grpc-proxy)
21
+
* Coherence CE 22.06 or later (or equivalent non-open source editions) with a configured [gRPC Proxy](https://github.com/oracle/coherence/tree/master/prj/coherence-grpc-proxy)
22
22
* Node 14
23
-
* NPM 6.x
23
+
* NPM 8.x
24
24
25
25
### Usage
26
26
27
27
Before testing the library, you must ensure a Coherence cluster is available. For local development, we recommend using the Coherence CE Docker image; it contains everything necessary for the client to operate correctly.
28
28
29
29
```bash
30
-
docker run -d -p 1408:1408 oraclecoherence/coherence-ce:21.12.1
30
+
docker run -d -p 1408:1408 oraclecoherence/coherence-ce:22.06
31
31
```
32
32
33
33
For more details on the image, see the [documentation](https://github.com/oracle/coherence/tree/master/prj/coherence-docker).
@@ -39,7 +39,7 @@ project's `package.json`:
39
39
```
40
40
...
41
41
"dependencies": {
42
-
"@oracle/coherence": "^1.0.0",
42
+
"@oracle/coherence": "^1.1.0",
43
43
},
44
44
...
45
45
```
@@ -56,8 +56,8 @@ such as maps and/or caches. When using the Coherence JavaScript Client, a `Sessi
56
56
gRPC endpoint and uses a specific serialization format to marshal requests and responses.
57
57
This means that different sessions using different serializers may connect to the same server endpoint. Typically,
58
58
for efficiency the client and server would be configured to use matching serialization formats to avoid
59
-
deserialization of data on the server but this does not have to be the case. If the server is using a different
60
-
serializer for the server-side caches it must be able to deserialize the client's requests, so there must be
59
+
deserialization of data on the server, but this does not have to be the case. If the server is using a different
60
+
serializer for the server-side caches, it must be able to deserialize the client's requests, so there must be
61
61
a serializer configured on the server to match that used by the client.
62
62
63
63
> NOTE: Currently, the Coherence JavaScript client only supports JSON serialization
@@ -122,18 +122,19 @@ by JavaScript except for the following differences:
122
122
* insertion order is not maintained
123
123
*`set()` calls cannot be chained because of the asynchronous nature of the API
124
124
125
-
> NOTE: The only difference between `NamedCache` and `NamedMap` is that the 'NamedCache' allows associating a
125
+
> NOTE: The only difference between `NamedCache` and `NamedMap` is that the 'NamedCache' allows associating a
126
126
> `time-to-live` on the cache entry, while `NamedMap` does not
127
127
128
-
For the following examples, let's assume that we have a Map defined in Coherence named `Test`. To get access to the map from the client:
128
+
For the following examples, let's assume that we have a Map defined in Coherence named `Test`.
129
+
To get access to the map from the client:
129
130
130
131
> NOTE: If using the Docker image previously mentioned for testing, you don't need to worry about the details of the map name. Any name will work.
131
132
132
133
```javascript
133
134
let map =session.getMap('Test')
134
135
```
135
136
136
-
Once we have the handle to our map, we can invoke the same basic operations as a standard JavaScript Map:
137
+
Once we have a handle to our map, we can invoke the same basic operations as a standard JavaScript Map:
Coherence provides developers with the ability to process some subset of the entries in a map,
215
-
resulting in an aggregated result. See the [documentation](https://oracle.github.io/coherence/21.12/api/java/index.html) for aggregators provided by this client.
216
+
resulting in an aggregated result. See the [documentation](https://oracle.github.io/coherence/22.06/api/java/index.html) for aggregators provided by this client.
216
217
217
-
Assuming the same set of keys and values are present from the filtering example above:
218
+
Assume the same set of keys and values are present from the filtering example above:
An entry processor allows mutation of map entries in-place within the cluster instead of bringing the entire object
237
-
to the client, updating, and pushing the value back. See the [documentation](https://oracle.github.io/coherence/21.12/api/java/index.html) for the processors provided by this client.
238
+
to the client, updating, and pushing the value back. See the [documentation](https://oracle.github.io/coherence/22.06/api/java/index.html) for the processors provided by this client.
238
239
239
-
Assuming the same set of keys and values are present from the filtering and aggregation examples:
240
+
Assume the same set of keys and values are present from the filtering and aggregation examples:
0 commit comments