Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7A0E0C98C for ; Tue, 15 May 2012 18:46:38 +0000 (UTC) Received: (qmail 44308 invoked by uid 500); 15 May 2012 18:46:38 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 44233 invoked by uid 500); 15 May 2012 18:46:38 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 44225 invoked by uid 99); 15 May 2012 18:46:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 May 2012 18:46:38 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of orwittmann@googlemail.com designates 209.85.214.47 as permitted sender) Received: from [209.85.214.47] (HELO mail-bk0-f47.google.com) (209.85.214.47) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 May 2012 18:46:31 +0000 Received: by bkcjm2 with SMTP id jm2so5443249bkc.6 for ; Tue, 15 May 2012 11:46:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=0a1lNxwKJK2a9tXPdCVqYulfXmb4DZuADFVMoy/wzHI=; b=EYhLwRs69wRiZKL9yuYPnpWNPf4ocDYR9hUhK48NjJ+0WCHoo7h9f2cS3ZFZkoAECL 6ORvik4ShbNgG2g1ngOBpM2kHCjyMgCu7py1ACAgEv+sPGEhfSGZXrBzpb1UX4mQA0oA 4XZPo3LuAczMcFMXQcg2n/XQn61urOv498DxokaBYBqEcue4BkwmMH404Y2HT/HC1NaW pyicJHfg+XZbdqulWDT74X8T2Lz94QvxHspMx3cPFeay4/SQasqgW5A7cYARLxyCKLzE DSasXVpWF0W82LUSfPf1cfnm2VPnb/mtRb28VMay4XkFdMV0eJNEsohVM46fHWjphB9w NGgQ== Received: by 10.204.151.81 with SMTP id b17mr18903bkw.52.1337107570323; Tue, 15 May 2012 11:46:10 -0700 (PDT) Received: from jasna.speedport.ip (p548CC7BC.dip.t-dialin.net. [84.140.199.188]) by mx.google.com with ESMTPS id e20sm11631706bkw.3.2012.05.15.11.46.08 (version=SSLv3 cipher=OTHER); Tue, 15 May 2012 11:46:09 -0700 (PDT) Message-ID: <4FB2A466.1030100@googlemail.com> Date: Tue, 15 May 2012 20:45:58 +0200 From: Oliver-Rainer Wittmann User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; de; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: [UPDATE SERVICE] proposal for a AOO 3.4 update service References: <4FB247E8.3020507@googlemail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, Am 15.05.12 16:11, schrieb Rob Weir: > On Tue, May 15, 2012 at 8:11 AM, Oliver-Rainer Wittmann > wrote: >> Hi, >> >> From my point of view it would make sense to reactivate a simple update >> service for AOO 3.4. >> >> The update URL for AOO 3.4 is: >> http://update38.services.openoffice.org/ProductUpdateService/check.Update >> (plus a query part ?pkgfmt= for non-Windows platforms) >> >> As this URL resolves to nothing, the user currently gets the following >> response from the update functionality in AOO 3.4: >> Status: Checking for an update failed. >> Description: General Internet error has occurred. >> >> I propose provide the following XML document when a HTTP GET request to the >> above given URL is made: >> >> > xmlns:inst="http://installation.openoffice.org/description"> >> >> >> Kay already made such an XML document available at: >> http://www.openoffice.org/ProductUpdateService/check.Update >> >> This response would allow the update functionality in AOO 3.4 to return to >> the user that the version is up to date. >> >> Thus, to reactivate an working update service for AOO 3.4 a redirection is >> needed. >> > > Are proposing that we just have a static XML file and redirect the > requests so it loads that static file? > Yes, as a short-term and fast solution. > I can see that as being a useful short-term solution. But soon we'll > need some more complicated logic, right? For example, when we enable > the 3.3. update check, we'll need to know that updates are available > for some languages, but not others. Can we do that all with > redirection to static files? Or do we need server-based logic, i.e., > a cgi script? > Static files would be possible, because each version has its own update service URL, but it would be not the best solution for the long-term. Thus, some server-based logic would make sense. > If we're going to need a cgi script in the end, I wonder if it makes > sense to start with one now? We could have a simply script that today > just always points to the "no update available" XML for AOO 3.4. But > then we make it more complicated as we go. > I am currently in preparation of a proposal for an update service for OOo 3.3 installations. Here, I can/will demonstrate how a server-based logic would look like. >> Can somebody make this happen? >> I have to admit that do not have the knowledge to do it on my own. >> > > If we just redirect to a static file, I think you can just enter a > JIRA request for Infra. If we go with a cgi script then we need > someone to develop that script first. > If nobody objects, I would go for this short-term and static approach and would ask via JIRA request for Infra, if the redirect to the already existing static file can be established. Best regards, Oliver.