Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@locus.apache.org Received: (qmail 27235 invoked from network); 21 Jan 2009 07:18:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Jan 2009 07:18:36 -0000 Received: (qmail 89029 invoked by uid 500); 21 Jan 2009 07:18:36 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 89011 invoked by uid 500); 21 Jan 2009 07:18:36 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 89000 invoked by uid 99); 21 Jan 2009 07:18:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Jan 2009 23:18:36 -0800 X-ASF-Spam-Status: No, hits=-2.8 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [194.138.12.131] (HELO mxs1.siemens.at) (194.138.12.131) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jan 2009 07:18:27 +0000 Received: from vies1k7x.sie.siemens.at ([158.226.129.83]) by mxs1.siemens.at with ESMTP id n0L7I5Hh011847 for ; Wed, 21 Jan 2009 08:18:05 +0100 Received: from nets139a.ww300.siemens.net ([192.168.217.3]) by vies1k7x.sie.siemens.at (8.12.11.20060308/8.12.1) with ESMTP id n0L7I5TD010351 for ; Wed, 21 Jan 2009 08:18:05 +0100 Received: from nets13ja.ww300.siemens.net ([158.226.250.79]) by nets139a.ww300.siemens.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 21 Jan 2009 08:18:04 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: AW: REST API Thoughts Date: Wed, 21 Jan 2009 08:18:03 +0100 Message-ID: <30DB6ACF50A0A3439F39EFEB1C52E166049C6F90@nets13ja.ww300.siemens.net> In-Reply-To: <30DB6ACF50A0A3439F39EFEB1C52E166078F2284@nets13ja.ww300.siemens.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: REST API Thoughts Thread-Index: Acl7kWVXGtZNNP2fT46xLI1tc72LSQABseWQ References: <30DB6ACF50A0A3439F39EFEB1C52E166078F2284@nets13ja.ww300.siemens.net> From: "Hirsch, Richard" To: X-OriginalArrivalTime: 21 Jan 2009 07:18:04.0726 (UTC) FILETIME=[66D52560:01C97B98] X-purgate: clean X-purgate: This mail is considered clean X-purgate-type: clean X-purgate-Ad: Checked for Spam by eleven - eXpurgate www.eXpurgate.net X-purgate-ID: 149917::090121081805-0B9DFBA0-479B56C9/0-0/0-15 X-purgate-size: 694/0 X-Virus-Checked: Checked by ClamAV on apache.org We might have to discuss would might happen if we added functionality to = a REST API function from Twitter. My suggestion would be: no problem as = long as the twitter functionality isn't broken.=20 D.=20 -----Urspr=FCngliche Nachricht----- Von: Hirsch, Richard=20 Gesendet: Mittwoch, 21. J=E4nner 2009 07:28 An: esme-dev@incubator.apache.org Betreff: REST API Thoughts What about if we based our fundamental REST API on that of Twitter. We = wouldn't have a ESME REST API with all functionality and then the = Twitter API rather we would have a Twitter API and then a smaller REST = API that would contain functionality not covered by Twitter. =20 Thoughts? =20 D,=20