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 client in such a scenario will also likely have the server-side business logic. right - is that what you have in mind?
Currently, there's already an excellent java client library Hector ( https://github.com/rantav/hector) and a Thrift API (allows cross-language rpc kind of like a web-service mediator/engine). So, there are good client-integration options with 'almost' minimal external lib dependencies. Especially with java, imho, additional binary dependencies that result in the jar-hell phenomenon is quite irksome for most users. Axis has a few lib dependencies of its own, too. -gshx On Sun, Jan 16, 2011 at 11:50 AM, 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/ >
