Red Hat Bugzilla – Bug 965345
RFE Interoperability between different protocols (REST, Memcached, Embedded)
Last modified: 2014-01-15 19:03:09 EST
Read and write data from clients with different protocols.
Interoperability chapter added to the Developer Guide.
3 topics so far.
20.3. Protocol Interoperability
- Enable Compatibility Mode Declaratively
This code snippet is for server mode. It's not applicable to library JDG. We should mention that this is a configuration for server.
- Enable Compatibility Mode Programmatically
This is in turn relevant only for library JDG, not for server. We should mention that this is only for Library mode and potentially provide
also a declarative configuration for library mode.
Question? Why are all these comments private?
20.3.2. Protocol Interoperability Over REST
This is quite a useful topic but personally I would rename it to something like "Reading Data Over Rest In Compatibility Mode". Of course, there could be much more information added. In this case, though, I think it'd be best to point users to some tests in upstream because there are so many combinations of types of data that it's hard to describe via plain text, and time consuming.
20.3.3. Protocol Interoperability Using the Command Line Interface
I don't understand the topic much. It should precisely specify where the options must be set. It also mentions "ispncon" which is a tool we don't support.
Could you please suggest any updates to
20.3.2. Protocol Interoperability Over REST, per your comment 13
OK, the only change I suggest is changing the sentence starting with "If custom objects have been serialized and stored via the remote cache, these can ..." to "If custom objects have been serialized and stored via the embedded or remote cache, these can ..."
Let's not complicate it now.
Thanks for your prompt feedback Martin and Divya and thank you for implementing them Mandar.
FYI Martin, as a general rule we set to comments to Private when linking to internal tools like the docbuilder.
Martin and Divya are any further changes required?
I will set this to ON QA once the docs are brewed later today if there are no further changes.
Looks good now.
Setting this bug to ON_QA.
Please move this bug to Verified if there are no further changes.
The fix for this bug is now generally released and available here: