Este contenido no está disponible en el idioma seleccionado.
Chapter 44. Endpoint Interoperability
Clients exchange data with Red Hat JBoss Data Grid through endpoints such as REST or Hot Rod.
Each endpoint uses a different protocol so that clients can read and write data in the cache in a suitable storage format. Because JBoss Data Grid can interoperate with multiple clients at the same time, it must convert data between client formats and the storage formats.
To configure JBoss Data Grid endpoint interoperability, you should define the media type that sets the format for data stored in the cache.
44.1. Considerations with Media Types and Endpoint Interoperability
Configuring Red Hat JBoss Data Grid to store data with a specific media type affects client interoperability.
REST clients generally handle text formats such as JSON, XML, or plain text better than binary formats. Although the JBoss Data Grid REST API does handle binary formats represented as String, encoded in hexadecimal or base64 format.
Java Hot Rod clients are suitable for handling Java objects that represent entities that reside in the cache. Java Hot Rod clients use marshalling operations to serialize and deserialize those objects into byte arrays.
Similarly, non-Java Hot Rod clients, such as the C++, C#, and Javascript clients, are suitable for handling objects in the respective languages. However, non-Java Hot Rod clients can interoperate with Java Hot Rod clients using platform independent data formats.
44.1.1. REST and Hot Rod Interoperability with Text-Based Storage
You can configure key and values with a text-based storage format.
For example, specify text/plain; charset=UTF-8, or any other character set, to set plain text as the media type. You can also specify a media type for other text-based formats such as JSON (application/json) or XML (application/xml) with an optional character set.
The following example configures the cache to store entries with the text/plain; charset=UTF-8 media type:
<cache>
<encoding>
<key media-type="text/plain; charset=UTF-8"/>
<value media-type="text/plain; charset=UTF-8"/>
</encoding>
</cache>
To handle the exchange of data in a text-based format, you must configure Hot Rod clients with the org.infinispan.commons.marshall.StringMarshaller marshaller.
REST clients must also send the correct headers when writing and reading from the cache, as follows:
-
Write:
Content-Type: text/plain; charset=UTF-8 -
Read:
Accept: text/plain; charset=UTF-8
| This configuration is compatible with… | |
|---|---|
| REST clients | Yes |
| Java Hot Rod clients | Yes |
| Non-Java Hot Rod clients | No |
| Querying and Indexing | No |
| Custom Java objects | No |
44.1.2. Java and Non-Java Client Interoperability with Protobuf
Storing data in the cache as Protobuf encoded entries provides a platform independent configuration that enables Java and Non-Java clients to access and query the cache from any endpoint.
If indexing is configured for the cache, JBoss Data Grid automatically stores keys and values with the application/x-protostream media type.
If indexing is not configured for the cache, you can configure it to store entries with the application/x-protostream media type as follows:
<distributed-cache name="my-cache">
<encoding>
<key media-type="application/x-protostream"/>
<value media-type="application/x-protostream"/>
</encoding>
</distributed-cache>
JBoss Data Grid converts between application/x-protostream and application/json, which allows REST clients to read and write JSON formatted data. However REST clients must send the correct headers, as follows:
- Read Header
Read: Accept: application/json
- Write Header
Write: Content-Type: application/json
The application/x-protostream media type uses Protobuf encoding, which requires you to register a Protocol Buffers schema definition that describes the entities and marshallers that the clients use. See Protobuf Encoding.
| This configuration is compatible with… | |
|---|---|
| REST clients | Yes |
| Java Hot Rod clients | Yes |
| Non-Java Hot Rod clients | Yes |
| Querying and Indexing | Yes |
| Custom Java objects | Yes |
