Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 85984 invoked from network); 23 Mar 2009 09:34:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Mar 2009 09:34:49 -0000 Received: (qmail 31850 invoked by uid 500); 23 Mar 2009 09:34:49 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 31809 invoked by uid 500); 23 Mar 2009 09:34:49 -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 31798 invoked by uid 99); 23 Mar 2009 09:34:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Mar 2009 09:34:49 +0000 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 (nike.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; Mon, 23 Mar 2009 09:34:39 +0000 Received: from vies1k7x.sie.siemens.at ([158.226.129.83]) by mxs1.siemens.at with ESMTP id n2N9YHBP017592 for ; Mon, 23 Mar 2009 10:34:18 +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 n2N9YHub020039 for ; Mon, 23 Mar 2009 10:34:17 +0100 Received: from nets13ja.ww300.siemens.net ([158.226.250.79]) by nets139a.ww300.siemens.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 23 Mar 2009 10:34:17 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Other twitter functionality to implement Date: Mon, 23 Mar 2009 10:34:16 +0100 Message-ID: <30DB6ACF50A0A3439F39EFEB1C52E16607CF24BA@nets13ja.ww300.siemens.net> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Other twitter functionality to implement Thread-Index: AcmpKram181KCXhGRIOXF6Vja1vmuACbMVPg References: <5a75db780903191452q5f4d518by8b5c5e06f98de8ac@mail.gmail.com> From: "Hirsch, Richard" To: X-OriginalArrivalTime: 23 Mar 2009 09:34:17.0021 (UTC) FILETIME=[891926D0:01C9AB9A] 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::090323103417-0B9DABA0-3494F67D/0-0/0-15 X-purgate-size: 853/0 X-Virus-Checked: Checked by ClamAV on apache.org I was exploring the Twitter REST API and was comparing to what we currently support. Although there is some functionality (favorites, block, etc.), there are still some functionality that is open.=20 What about supporting the deletion of messages? * statuses/destroy Destroys the status specified by the required ID parameter. The authenticating user must be the author of the specified status. I know this currently isn't possible in ESME but I think it is a functionality that is useful. Of course, the inclusion of pools would influence the future implementation (think of pools in which messages can't be deleted based on compliance reasons) but until we have developed pools, the deletion of messages would still be useful.=20 Added a Jira item for this: https://issues.apache.org/jira/browse/ESME-51 Thoughts? D.=20