[JBoss JIRA] Created: (ISPN-313) Provide an StandaloneJGroupsChannelLookup implementation
by Galder Zamarreno (JIRA)
Provide an StandaloneJGroupsChannelLookup implementation
--------------------------------------------------------
Key: ISPN-313
URL: https://jira.jboss.org/jira/browse/ISPN-313
Project: Infinispan
Issue Type: Feature Request
Components: RPC
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Fix For: 4.1.0.BETA1
StandaloneJGroupsChannelLookup would target environments that are
either standalone or within other app servers that are not JBoss.
It would allow for different Infinispan configurations to use the same
shared transport, reducing network configuration.
Infinispan and StandaloneJGroupsChannelLookup, if you guys create
such a class, have it use the ChannelFactory.createChannel(String
stack_name) method, not the old legacy createMultiplexerChannel method
used by JBC. ChannelFactory.createChannel(String stack_name) will be a
stable API, createMultiplexerChannel(...) may go away in JGroups 3.0.
ChannelFactory.createChannel(String stack_name) lets you get a shared
transport channel if the stack's transport protocol config has the
singleton_name element.
Full thread can be found in forum reference link
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (ISPN-508) ProtoBuf as portable serialization for Hot Rod
by Galder Zamarreno (JIRA)
ProtoBuf as portable serialization for Hot Rod
----------------------------------------------
Key: ISPN-508
URL: https://jira.jboss.org/browse/ISPN-508
Project: Infinispan
Issue Type: Feature Request
Components: Cache Server
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Fix For: 5.0.0.Final
Consider using Google ProtoBufs as a way to serialize data into a wire so that a single Hot Rod server can simulatneously be accessed by clients written in different languages. At the moment, cos Java client uses standard serialization, only Java clients would really be able to understand the contents of it, unless there's a non-JVM implementation that can understand java serialization.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years