[
http://jira.jboss.com/jira/browse/JGRP-340?page=all ]
Bela Ban updated JGRP-340:
--------------------------
Description:
Things to be done:
- Use of Streamable rather than Externalizable
- Currently we use 1 thread per request rather than a thread pool, e.g. Executor !
- Better logging and diagnostics (JMX)
- Use of NIO to prevent the 1 thread/client scalability issue
- GossipClient and RouterStub should use common, shared code to communicate with the
GossipRouter, currently there are exceptions because these 2 classes don't even use
the same network format ! Besides, we can refactor redundant code into a common
superclass
- Use of ConnectionTable(NIO) ?
- Add configuration options for GossipRouter's sockets, e.g. send/receive buffer size,
nagling, keep_alive etc
- Support of UDP
was:
Things to be done:
- Use of Streamable rather than Externalizable
- Currently we use 1 thread per request rather than a thread pool, e.g. Executor !
- Better logging and diagnostics (JMX)
- Use of NIO to prevent the 1 thread/client scalability issue
- GossipClient and RouterStub should use common, shared code to communicate with the
GossipRouter, currently there are exceptions because these 2 classes don't even use
the same network format ! Besides, we can refactor redundant code into a common
superclass
- Use of ConnectionTable(NIO) ?
- Add configuration options for GossipRouter's sockets, e.g. send/receive buffer size,
nagling, keep_alive etc
Major overhaul of GossipRouter
------------------------------
Key: JGRP-340
URL:
http://jira.jboss.com/jira/browse/JGRP-340
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.6
Things to be done:
- Use of Streamable rather than Externalizable
- Currently we use 1 thread per request rather than a thread pool, e.g. Executor !
- Better logging and diagnostics (JMX)
- Use of NIO to prevent the 1 thread/client scalability issue
- GossipClient and RouterStub should use common, shared code to communicate with the
GossipRouter, currently there are exceptions because these 2 classes don't even use
the same network format ! Besides, we can refactor redundant code into a common
superclass
- Use of ConnectionTable(NIO) ?
- Add configuration options for GossipRouter's sockets, e.g. send/receive buffer
size, nagling, keep_alive etc
- Support of UDP
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira