Coherence 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 caches.
Coherence for .NET consists of 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).
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 INamedCache operations are being sent to a remote cluster node (over TCP/IP) is completely transparent to the client application.
Requirements, Installation and Deployment for Coherence for .NET
Skip to end of metadata Go to start of metadata
Page: Building Integratable Objects for .NET Clients Page: Configuration and Usage for .NET Clients Page: Configuring a Local Cache for .NET Clients Page: Configuring a Near Cache for .NET Clients Page: Continuous Query Cache for .NET Clients Page: Feature Requests - Coherence for .NET Page: Network Filters for .NET Clients Page: Remote Invocation Service for .NET Clients Page: Requirements, Installation and Deployment for Coherence for .NET Page: Sample Web Application for .NET Clients Page: Sample Windows Forms Application for .NET Clients Page: Special Considerations Regarding Web Applications for .NET Clients Page: Special Considerations Regarding Windows Forms Applications for .NET Clients