[
https://issues.apache.org/jira/browse/CASSANDRA-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741385#action_12741385
]
Eric Evans commented on CASSANDRA-241:
--------------------------------------
I was trying to make this as optional as possible, and the pattern cited above
doesn't support that.
For the vast majority of users this doesn't make any sense whatsoever; tweaking
it is more likely to break, rather than enable. I really didn't even want to
draw the sort of attention to it that an example entry in the sample config
provides (and I'm still sort of wishing it was less "documented").
However, since I already feel "beaten" by this issue I'll update the patch if
you feel it should be mandatory. :)
> move daemon to framed transport (thrift)
> ----------------------------------------
>
> Key: CASSANDRA-241
> URL: https://issues.apache.org/jira/browse/CASSANDRA-241
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.4
> Reporter: Eric Evans
> Assignee: Eric Evans
> Fix For: 0.4
>
> Attachments: 241.txt,
> v1-0001-CASSANDRA-241-optional-support-for-framed-transport.txt
>
>
> The framed transports in thrift wrap the underlying transport to prepend the
> message size as a 4 byte value. There are purported benefits to buffering,
> but the main purpose of these wrappers is to allow non-blocking servers to
> perform reads without deserialization. Of course, if the server transport is
> framed, the client's must be as well, and vice versa, (framed and non-framed
> transports are incompatible).
> CassandraDaemon is currently a threaded server with the default transport, I
> believe we should change it to being framed, for compatibility with
> non-blocking clients (this actually came up during an attempt to use a
> Twisted client).
> This will break all existing client apps, (even if fixing them is trivial).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
