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:05 PM, Gary Dusbabek <gdusba...@gmail.com> wrote: > 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 can find the results of the work here: > https://github.com/gdusbabek/cassandra > > Gary > > On Sun, Jan 16, 2011 at 10:50, indika kumara <ind...@apache.org> wrote: > > Hi All, > > > > What would you think about the idea of exposing the Cassandra as a Web > > Service so that any web service client can connect to the Cassandra > server? > > > > This would require embedding a web service engine in the server side, > > providing WSDL(s) for Cassandra’s services such as management, data > access, > > etc. > > > > If this task can be done, it is possible to connect to the Cassandra > through > > different languages, different transports such as TCP, HTTP, JMS, etc. > > Moreover, the connection between clients and the Cassandra can be secure > > (WS-Security), and reliable. > > > > If this task is worth, I may be able to contribute for implementing it. I > am > > familiar with the Axis2 web service engine [1], and an Apache committer. > > > > Your suggestions are welcome! > > > > Thanks, > > > > Indika > > > > [1] http://axis.apache.org/axis2/java/core/ > > >
