Infinispan Hot Rod: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 8: | Line 8: | ||
=HotRod Connector= | =HotRod Connector= | ||
The HotRod connector is configured in the [[Infinispan_Configuration#infinispan:server:endpoint_Section|infinispan:server:endpoint Section]]. | |||
For more details on HotRod clients and how they connect to a HotRod server: | |||
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | |||
:[[Infinispan_HotRod_Client#Relationship_between_RemoteCacheManager_and_a_Server-Side_Cache_Container|HotRod client API]] | |||
</blockquote> | |||
=HotRod Client= | =HotRod Client= | ||
Revision as of 01:43, 15 October 2016
Internal
Overview
HotRod is Infinispan’s custom binary, language neutral protocol for communication between clients and servers. The protocol was designed to enable faster interactions compared to other existing text based protocols and to allow clients to make more intelligent decisions with regards to load balancing, failover and even data location operations. When interacting with Infinispan via the Hot Rod protocol, it is mandated that keys and values are byte arrays, to ensure platform neutral behavior. HotRod does not know about objects and types.
HotRod Connector
The HotRod connector is configured in the infinispan:server:endpoint Section.
For more details on HotRod clients and how they connect to a HotRod server: