|
2 | 2 |
|
3 | 3 | Since its initial release in 2001, it has been used by thousands of customers across many industries to power some of the mission critical systems you use every day. Often imitated, but never duplicated, it is now available for everyone to use free of charge.
|
4 | 4 |
|
5 |
| -### About Oracle Coherence Client for .NET |
| 5 | +### About Oracle Coherence Extend Client for .NET |
6 | 6 |
|
7 |
| -**Oracle Coherence Client for .NET** allows .NET applications to access Coherence clustered services, including data, data events, and data processing from outside the Coherence cluster. Typical uses of Coherence for .NET include desktop and web applications that require access to Coherence-managed data. |
| 7 | +**Oracle Coherence Extend Client for .NET** allows .NET applications to access Coherence clustered services, including data, data events, and data processing from outside the Coherence cluster. Typical uses of Coherence for .NET include desktop and web applications that require access to Coherence-managed data. |
8 | 8 |
|
9 |
| -Coherence Client for .NET is a lightweight .NET library that connects to a Coherence\*Extend clustered service instance running within the Coherence cluster using a high performance TCP/IP-based communication layer. This library sends all client requests to the Coherence\*Extend clustered service which, in turn, responds to client requests by delegating to an actual Coherence clustered service (for example, a *Partitioned* or *Replicated* cache service). |
| 9 | +Coherence Extend Client for .NET is a lightweight .NET library that connects to a Coherence\*Extend clustered service instance running within the Coherence cluster using a high performance TCP/IP-based communication layer. This library sends all client requests to the Coherence\*Extend clustered service which, in turn, responds to client requests by delegating to an actual Coherence clustered service (for example, a *Partitioned* or *Replicated* cache service). |
10 | 10 |
|
11 | 11 | An `INamedCache` instance is retrieved via the `CacheFactory.GetCache()` API call. Once it is obtained, a client accesses the `INamedCache` in the same way as it would if it were part of the Coherence cluster. The fact that cache operations are being sent and executed on a remote cluster node (over TCP/IP) is completely transparent to the client application.
|
12 | 12 |
|
13 |
| -For more information, see [Oracle Coherence Client for .NET Documentation]((https://coherence.community/14.1.2.0/api/dotnet/index.html) |
| 13 | +For more information, see [Oracle Coherence Client for .NET Documentation](https://docs.oracle.com/en/middleware/fusion-middleware/coherence/14.1.2/net-reference) |
14 | 14 |
|
15 | 15 | ### Additional Information
|
16 | 16 |
|
17 | 17 | * [Oracle Coherence CE Web Site](https://coherence.community/)
|
18 | 18 | * [Oracle Coherence CE Blog](https://medium.com/oracle-coherence)
|
19 | 19 | * [Oracle Coherence YouTube Channel](https://www.youtube.com/user/OracleCoherence)
|
20 | 20 | * [Oracle Coherence CE Source Code](https://github.com/oracle/coherence)
|
21 |
| -* [Oracle Coherence Client for .NET Source Code](https://github.com/oracle/coherence-dotnet-extend-client/tree/main) |
| 21 | +* [Oracle Coherence Extend Client for .NET Source Code](https://github.com/oracle/coherence-dotnet-extend-client/tree/main) |
0 commit comments