[
https://issues.apache.org/jira/browse/CASSANDRA-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915897#action_12915897
]
Brandon Williams commented on CASSANDRA-1405:
---------------------------------------------
To do this, we'll need to make a CassandraServer.instance so that getProcessor
has a way to get to it to reset the ClientState (Brian's approach for
CASSANDRA-876 did this using StorageService.instance, which was already there.)
> Switch to THsHaServer, redux
> ----------------------------
>
> Key: CASSANDRA-1405
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1405
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 0.7.0
>
>
> Brian's patch to CASSANDRA-876 suggested using a custom TProcessorFactory
> subclass, overriding getProcessor to reset to a default state when a new
> client connects. It looks like this would allow dropping
> CustomTThreadPoolServer as well as allowing non-thread based servers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
