On 15-09-2010 19:16, Amol Deshpande wrote:
Hi,
Would there be any objections to the following code refactoring ?
1. Create a CassandraServerExceptionFactory class that returns various
exceptions that can be thrown by StorageProxy instead of thrift
exceptions.
2. Create a CassandraServerConsistencyLevel enum that is used instead of
thrift/avro definitions by the StorageProxy, with appropriate
translation methods between the enums (and perhaps a startup check
function that makes sure they are identical in value).
3. Create an AbstractCassandraServer superclass that exposes methods
like readColumnFamily in a transport-independent manner.
<insert here the standard newbie /i'm not worthy disclaimer>
That would also open for the possibility to support more then one
transport method on a single node. No?
Could be handy in the transition phase from thrift to avro.
And, one you implment his own transport layer.
./Morten
