Skip to content

Commit

Permalink
Remove note for concurrency primitives from readme (#604)
Browse files Browse the repository at this point in the history
  • Loading branch information
puzpuzpuz committed Sep 18, 2020
1 parent 6451ded commit 03b2002
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 3 deletions.
5 changes: 5 additions & 0 deletions DOCUMENTATION.md
Original file line number Diff line number Diff line change
Expand Up @@ -500,6 +500,11 @@ Hazelcast Node.js client supports the following data structures and features:
* Reliable Topic
* CRDT PN Counter
* Flake Id Generator
* FencedLock (CP Subsystem)
* Semaphore (CP Subsystem)
* AtomicLong (CP Subsystem)
* AtomicReference (CP Subsystem)
* CountDownLatch (CP Subsystem)
* Event Listeners
* Entry Processor
* Query (Predicates)
Expand Down
4 changes: 1 addition & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -120,14 +120,12 @@ Refer to [the documentation](DOCUMENTATION.md) to learn more about supported con
* Additional data structures and simple messaging constructs such as **Set**, **MultiMap**, **Queue**, **Topic**
* Cluster-wide unique ID generator, called **FlakeIdGenerator**
* Distributed, CRDT based counter, called **PNCounter**
* Primitives for distributed computing such as **Lock**, **Semaphore**, **Atomic Long** *
* Distributed concurrency primitives from CP Subsystem such as **FencedLock**, **Semaphore**, **AtomicLong**
* Integration with [Hazelcast Cloud](https://cloud.hazelcast.com/)
* Support for serverless and traditional web service architectures with **Unisocket** and **Smart** operation modes
* Ability to listen client lifecycle, cluster state and distributed data structure events
* and [many more](https://hazelcast.org/imdg/clients-languages/node-js/#client-features).

> *: Make sure to use 3.x versions of Hazelcast Node.js client and IMDG to access these primitives as the work to support them in 4.x versions is in progress.
## Getting Help

You can use the following channels for your questions and development/usage issues:
Expand Down

0 comments on commit 03b2002

Please sign in to comment.