Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 99C73100EA for ; Wed, 12 Mar 2014 20:25:08 +0000 (UTC) Received: (qmail 62306 invoked by uid 500); 12 Mar 2014 20:24:56 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 62161 invoked by uid 500); 12 Mar 2014 20:24:54 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 62050 invoked by uid 99); 12 Mar 2014 20:24:51 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Mar 2014 20:24:51 +0000 Date: Wed, 12 Mar 2014 20:24:51 +0000 (UTC) From: "Edward Capriolo (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-6846) Provide standard interface for deep application server integration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-6846?page=3Dcom.atlas= sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D= 13932302#comment-13932302 ]=20 Edward Capriolo commented on CASSANDRA-6846: -------------------------------------------- @Sylvain Lebresne=20 This is a brainstorming ticket. Placing a -1 on a brainstorm session is not= always constructive I would read: http://sostark.net/post/4965998605/tina-feys-rules-of-improvisation-that-wi= ll-change-your > 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: (=E2=95=AF=C2=B0=E2=96=A1=C2=B0)=E2=95=AF=EF=B8=B5= =E2=94=BB=E2=94=81=E2=94=BB, 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 i= nside Cassandra, I'd like to propose the creation an internal somewhat stab= le (versioned?) interface that could allow any app server to achieve deep i= ntegration with Cassandra, and as a result, these servers could=20 > 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 fo= r 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/j2= ee containers, I believe we could come up with a reasonable interface to al= low any jvm app server to be integrated and maintained in or out of the Cas= sandra 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 t= o be able to start building much more interestingly (and simply) tiered app= lications. -- This message was sent by Atlassian JIRA (v6.2#6252)