[ https://issues.apache.org/jira/browse/CASSANDRA-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938451#comment-13938451 ]
Edward Capriolo commented on CASSANDRA-6846: -------------------------------------------- To be more clear the goal is not to bring up N transports. The point is users may need to have some code that executes on startup/shutdown. It may be a daemon process, it may not be. This is just generalizing the hook. > Provide standard interface for deep application server integration > ------------------------------------------------------------------ > > Key: CASSANDRA-6846 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6846 > Project: Cassandra > Issue Type: New Feature > Components: API, Core > Reporter: Tupshin Harper > Assignee: Tupshin Harper > Priority: Minor > Labels: ponies > > Instead of creating a pluggable interface for Thrift, I'd like to create a > pluggable interface for arbitrary app-server deep integration. > Inspired by both the existence of intravert-ug, as well as there being a long > history of various parties embedding tomcat or jetty servlet engines inside > Cassandra, I'd like to propose the creation an internal somewhat stable > (versioned?) interface that could allow any app server to achieve deep > integration with Cassandra, and as a result, these servers could > 1) host their own apis (REST, for example > 2) extend core functionality by having limited (see triggers and wide row > scanners) access to the internals of cassandra > The hand wavey part comes because while I have been mulling this about for a > while, I have not spent any significant time into looking at the actual > surface area of intravert-ug's integration. But, using it as a model, and > also keeping in minds the general needs of your more traditional servlet/j2ee > containers, I believe we could come up with a reasonable interface to allow > any jvm app server to be integrated and maintained in or out of the Cassandra > tree. > This would satisfy the needs that many of us (Both Ed and I, for example) to > have a much greater degree of control over server side execution, and to be > able to start building much more interestingly (and simply) tiered > applications. -- This message was sent by Atlassian JIRA (v6.2#6252)