Thanks Gary A HTTP transport based on NIO [1] may offer a considerable
performance. I may implement it locally and compare the performance.
Indika
[1] http://hc.apache.org/httpcomponents-core-ga/httpcore-nio/index.html
On Mon, Jan 17, 2011 at 8:01 PM, Gary Dusbabek wrote:
> No, it's not i
No, it's not in trunk. I created the branch as a proof-of-concept
only. I can see the utility of a RESTful interface, but I doubt
you'll be able to achieve performance comparable to thrift.
Gary
On Mon, Jan 17, 2011 at 07:23, indika kumara wrote:
> Hi Gary,
>
> Thank you very much for the info
Hi Gary,
Thank you very much for the information. BTW, It seems that your transport
code is not in the Cassandra's trunk. Is it going add that code into the
trunk? BTW, do you think what I suggested would be worth? If so, I would
like to implement it.
Thanks,
Indika
On Mon, Jan 17, 2011 at 7:0
It wouldn't be hard to do. Cassandra is structured in such a way that
it is pretty easy to wrap a transport around a few classes that handle
most of the client interaction. Last September I created a
RESTful-like version of Cassandra in just a few hours. I haven't
maintained the branch, but you
Thank you for the information about the TServlet . I would only develop what
I suggested if the Cassandra community find that it is worth. BTW, it is
possible to write a non blocking HTTP/S transport that offers a significant
performance. Even the JMS may be worth.
Thanks,
Indika
On Mon, Jan 17,
If you have good stories for such an abstraction, then, it can live atop
thrift and extend Tom White's TServlet which is now a part of thrift:
http://svn.apache.org/viewvc/thrift/branches/0.6.x/lib/java/src/org/apache/thrift/server/TServlet.java
http://www.lexemetech.com/2007/09/java-servlet-for-th
Gaurav - I thought of enabling a WS-client to call Cassandra server nodes
directly. For that, there should be a web-service engine to process the
WS-requests in the server-side. A client can be any WS-client that can call
a service using the service's WSDL. A client can use different protocol such
Indika - what use cases do you have in mind for the ws-clients connecting
directly to Cassandra especially since you mention connections from clients
using ws-security? Are you suggesting remote connections over https directly
to the data-store between non-colocated client and server nodes? The cli
