Return-Path: 
 <ooo-dev-return-19381-apmail-incubator-ooo-dev-archive=incubator.apache.org@incubator.apache.org>
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 71EDBC316
	for <apmail-incubator-ooo-dev-archive@minotaur.apache.org>;
 Mon, 21 May 2012 11:55:53 +0000 (UTC)
Received: (qmail 66125 invoked by uid 500); 21 May 2012 11:55:52 -0000
Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org
Received: (qmail 65808 invoked by uid 500); 21 May 2012 11:55:51 -0000
Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ooo-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:ooo-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:ooo-dev@incubator.apache.org>
List-Id: <ooo-dev.incubator.apache.org>
Reply-To: ooo-dev@incubator.apache.org
Delivered-To: mailing list ooo-dev@incubator.apache.org
Received: (qmail 65785 invoked by uid 99); 21 May 2012 11:55:51 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 May 2012 11:55:50 +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; Mon, 21 May 2012 11:55:44 +0000
Received: by bkcjm2 with SMTP id jm2so4117534bkc.6
        for <ooo-dev@incubator.apache.org>;
 Mon, 21 May 2012 04:55:23 -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=himIaSSm/bQAJ1R6buQc7RuZ3Evoo+KnXimbN6UzZXQ=;
        b=mGMSa6l57GK3ffVitGTXmEcp2FHWcJZaeCNaWlXoEujWVph7dRDeuZKUydcFURHOfP
         lUYZ5u4VdKuRk10SjTds5VQOQawHTpiBotoc7PCm866f4nELAl0edo/7tZQVKEXhE53p
         yZkXlw83FFCgPip15Bv2dhC7pLHMEz/wATbIG9P77SmEbKRY+VJiHiwCgU2gzGgXu2Id
         Zmd7E59wwLUh96/LtRh0ZghK4yLDW8U8/iS9Ue4Czs5HJCp9sOkbHtHxgPdWxrq/8htu
         khRHwxEsxdQ0m9Z/96cIbplHICgOX6kXi65jqqu0UaptW9agJ5yIC1FBAcSaJ/3Fzc3h
         lSjQ==
Received: by 10.204.156.24 with SMTP id u24mr7521270bkw.75.1337601323274;
        Mon, 21 May 2012 04:55:23 -0700 (PDT)
Received: from [9.155.131.111] (deibp9eh1--blueice2n2.emea.ibm.com.
 [195.212.29.172])
        by mx.google.com with ESMTPS id fu14sm502565bkc.13.2012.05.21.04.55.21
        (version=SSLv3 cipher=OTHER);
        Mon, 21 May 2012 04:55:22 -0700 (PDT)
Message-ID: <4FBA2D2A.7090908@googlemail.com>
Date: Mon, 21 May 2012 13:55:22 +0200
From: Oliver-Rainer Wittmann <orwittmann@googlemail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:12.0) Gecko/20120428 Thunderbird/12.0.1
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>
 <CAP-ksoicP8evJxtzSL1KVibR_qJP8NsbUKemRf2hqhsMBuRTWA@mail.gmail.com>
 <4FB2A466.1030100@googlemail.com>
In-Reply-To: <4FB2A466.1030100@googlemail.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Hi,

On 15.05.2012 20:45, Oliver-Rainer Wittmann wrote:
> Hi,
>
> Am 15.05.12 16:11, schrieb Rob Weir:
>> On Tue, May 15, 2012 at 8:11 AM, Oliver-Rainer Wittmann
>> <orwittmann@googlemail.com> 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=<pkgformat> 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:
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <inst:description
>>> xmlns:inst="http://installation.openoffice.org/description">
>>> </inst: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.
>

Ok, let us drive this issue a little bit more.

For the static and short-term update service for AOO 3.4 I will do the following:
- Creation of HTTP resource [1] provided the above given simple XML document
- Asking ASF Infrastructure via corresponding JIRA issue to redirect HTTP GET 
requests for URL [2] (Update URL of AOO 3.4) to URL [2]

[1] http://www.openoffice.org/projects/update38/ProductUpdateService/check.Update
[2] http://update38.services.openoffice.org/ProductUpdateService/check.Update


Best regards, Oliver.