Return-Path: Delivered-To: apmail-felix-dev-archive@www.apache.org Received: (qmail 28986 invoked from network); 27 Jan 2009 20:37:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Jan 2009 20:37:55 -0000 Received: (qmail 34212 invoked by uid 500); 27 Jan 2009 15:43:06 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 34160 invoked by uid 500); 27 Jan 2009 15:43:06 -0000 Mailing-List: contact dev-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@felix.apache.org Delivered-To: mailing list dev@felix.apache.org Received: (qmail 34148 invoked by uid 99); 27 Jan 2009 15:43:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jan 2009 07:43:06 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [66.134.204.98] (HELO sausalito.ascert.com) (66.134.204.98) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jan 2009 15:42:55 +0000 Received: from [127.0.0.1] ([10.253.130.14] unverified) by sausalito.ascert.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 27 Jan 2009 07:42:31 -0800 Message-ID: <497F2B52.80104@ascert.com> Date: Tue, 27 Jan 2009 17:42:10 +0200 From: Rob Walker Organization: Ascert LLC User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: dev@felix.apache.org Subject: Re: HTTP service implementation work... References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 27 Jan 2009 15:42:31.0668 (UTC) FILETIME=[DDD07B40:01C98095] X-Virus-Checked: Checked by ClamAV on apache.org Marcel We're an active user of the Http Service - it's the foundation of our most recent GWT based web served application. Like you say, there aren't any tests in there, but I'll happily give any new versions you create a spin in our App environment and see if anything breaks. I closed a few JIRA issues that we needed recently - specifically ensuring that timestamps were correctly returned so that browser and proxy caching worked properly, adding a service property (forget who asked for this), and a few other minor mods. In the process, I also tweaked some alias handling which wasn't quite working to spec. All of these are checked in, so the SVN logs show what we changed. I don't have any work in progress here that isn't checked in, so from my side - go ahead. I'd hoped myself to tackle a few of the issues, but probably won't get a chance over next few weeks. Happy if there's ways I can help out or act as a sounding board for ideas though. Regards -- Rob Marcel Offermans wrote: > Is anybody currently working on any aspects of the HTTP service > implementation? There is quite a list of issues in JIRA: > > http://issues.apache.org/jira/browse/FELIX/component/12310340 > > I need some new features, so I'd like to get started, but I don't want > to duplicate any work. > > Also, who is using this bundle now? Since there are no tests for it, > making changes might break things, so having people that use the > bundle and can re-test a new version might help. > > Greetings, Marcel > -- Ascert - Taking systems to the Edge robw@ascert.com +44 (0)20 7488 3470 www.ascert.com