Return-Path: 
 <ooo-dev-return-18911-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 108E9C540
	for <apmail-incubator-ooo-dev-archive@minotaur.apache.org>;
 Wed, 16 May 2012 17:28:04 +0000 (UTC)
Received: (qmail 79497 invoked by uid 500); 16 May 2012 17:28:03 -0000
Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org
Received: (qmail 79413 invoked by uid 500); 16 May 2012 17:28:03 -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 79404 invoked by uid 99); 16 May 2012 17:28:03 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2012 17:28:03 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_FRT_PACKAGE
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of kay.schenk@gmail.com designates
 209.85.217.175 as permitted sender)
Received: from [209.85.217.175] (HELO mail-lb0-f175.google.com)
 (209.85.217.175)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2012 17:27:56 +0000
Received: by lbol5 with SMTP id l5so733864lbo.6
        for <ooo-dev@incubator.apache.org>;
 Wed, 16 May 2012 10:27:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=YBRbEyLGomBKkMy+iHNz+3Hqc6y1a0Sw/nXhghVpBk4=;
        b=vqm2ZsgTw8CEveffPI0lpU9PwBA+aYcyx94IpuYxQDLw0cHehRKzzE+bQBZiDpkhz1
         WGGRjvyYXcskd/dH8wfsrfJixFpp5RZU+3+UwVdvC6Vm2ATjJcxtsuBMZcrVfa4AG7ph
         l0TCI0FVVFxtAign2z/p1rqAuVgxX5lKkU3SebYAC35rJFy2/47Gl2HUIre9RboHW6UU
         KMrqCNSVHfIHV5xI7VZe7SNP4uy/4CnuZoq6p+bK5EyG5S4Qgx5tjtxC6luCHVd6Tzx/
         pKfeB1If5nTqWd2+Ie5ZznRvWp30j+JOwAduopm0F1obiu7SmJuku0zb1DvhW81kMBSs
         uIcA==
MIME-Version: 1.0
Received: by 10.152.109.198 with SMTP id hu6mr4117346lab.21.1337189256478;
 Wed, 16 May 2012 10:27:36 -0700 (PDT)
Received: by 10.112.60.67 with HTTP; Wed, 16 May 2012 10:27:36 -0700 (PDT)
In-Reply-To: <4FB38E67.7040406@googlemail.com>
References: <4FB38E67.7040406@googlemail.com>
Date: Wed, 16 May 2012 10:27:36 -0700
Message-ID: 
 <CAGj3216r-Su6rJSrsY6mP48G42cFJdc12ibQBwoOhpB9x4TXjA@mail.gmail.com>
Subject: Re: [UPDATE SERVICE] proposal a OOo 3.3 update service
From: Kay Schenk <kay.schenk@gmail.com>
To: ooo-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=bcaec54b49d6a13ea304c02aa2a2

--bcaec54b49d6a13ea304c02aa2a2
Content-Type: text/plain; charset=ISO-8859-1

On Wed, May 16, 2012 at 4:24 AM, Oliver-Rainer Wittmann <
orwittmann@googlemail.com> wrote:

> Hi,
>
> as our release AOO 3.4 is out now for more than a week I think it would
> make sense to reactivate a simple update service for installed OOo 3.3
> versions.
> I have already seen a post on the users mailing list that the update
> functionality is not working in OOo 3.3. I assume that corresponding posts
> also exist in the forum.
> From my point of view it is time to let our OOo 3.3 users know via the
> update functionality that we have released AOO 3.4.
>
> The update URL for OOo 3.3 is:
> http://update36.services.**openoffice.org/**ProductUpdateService/check.**
> Update<http://update36.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 OOo 3.3:
> Status: Checking for an update failed.
> Description: Error reading data from the network.
> Server error message: Could not read status line: An existing connection
> was forcibly closed by the remote host.
>
> There are two solutions:
>
> (A) "static" solution:
> Provide an XML document similar to the one which is attached when an HTTP
> GET request to the above given URL is made.
> The attached XML document contains an atom feed according to [1]
> Currently, it only contains entries for:
> - German, Windows
> - German, MacOS X
> - German, Linux, 32bit
> - German, Linux, 64bit
> - English-US, Windows
> I hope I got the inst:os and inst:arch content right for all the platforms.
> For Windows and MacOS we could directly provide download links. Thus, the
> update functionality can download it and install it on corresponding user
> demand.
> For Linux we can not distinguish the different needed package formats in
> this "static" solution - as far as I know. Thus, a landing page can be
> given here. The update functionality can open it in the user's default
> browser on corresponding user demand. In the attached XML document I
> included our AOO 3.4 release announcement page as this landing page - this
> is only a proposal.
> The final XML document needs to be extended by entries for all possible
> combinations. This would mean 4 entries (Windows, MacOS X, Linux 32bit,
> Linux 64bit) for each language which we had released for AOO 3.4.
> It would be also be possible to include more combinations for which we
> have no package. We could create a special landing page for these which
> state that AOO 3.4 is out and that the user might want to have a look, if
> one of the provided packages would fit her/his needs.
>
> For this solution we need to provide the XML document at the above given
> URL.
>

Oliver--

Hi. OK, a dumb question...have you ascertained that this doc actually
works? That is, have you tested it with some sort of URL redirect?

Right now, we have an area on the web server that could house this...in

/projects/update36/ProductUpdateService

If you overwrite check.Update with this file, and do a local host setup,
your own /etc/hosts, and redirect update36.services.openoffice.org to

140.211.11.131

you could test it out

One of the problems we will run into, esp for Linux (I don't know about
other platforms) is that the user has a appended "pkgfmt" already on the
update URL, so in my experimenting, the update call failed because an
acceptable package was not found.

Your analysis about just leading linux folks to the url of a page for an
update is great, but what to do about the existing information?

Anyway, copy your doc over to the web server, setup the redirect, and let
us know how things go.




>
> (B) "dynamic" solution:
> As the HTTP GET request contains all the information needed to identify
> the installed version performing the HTTP GET request - see [2], with some
> server-side logic an XML document could be dynamically created which
> servers the identified version.
> E.g.:
> <?xml version="1.0" encoding="UTF-8"?>
> <inst:description xmlns:inst="http://**installation.openoffice.org/**
> description <http://installation.openoffice.org/description>">
>    <inst:version>- Apache OpenOffice 3.4</inst:version>
>    <inst:buildid>9590</inst:**buildid>
>    <inst:os>Linux</inst:os>
>    <inst:arch>x86</inst:arch>
>    <inst:update type="application/octet-**stream" src="
> http://sourceforge.net/**projects/openofficeorg.mirror/**
> files/stable/3.4.0/Apache_**OpenOffice_incubating_3.4.0_**
> Linux_x86_install-deb_en-US.**tar.gz/download<http://sourceforge.net/projects/openofficeorg.mirror/files/stable/3.4.0/Apache_OpenOffice_incubating_3.4.0_Linux_x86_install-deb_en-US.tar.gz/download>"
> />
> </inst:description>
> which would serve a OOo 3.3, en-US, Linux 32bit, packgage format deb
> If there is no AOO 3.4 for the identified OOo 3.3 the script should create
> the following XML document:
> <?xml version="1.0" encoding="UTF-8"?>
> <inst:description xmlns:inst="http://**installation.openoffice.org/**
> description <http://installation.openoffice.org/description>">
> </inst:description>
>
> For this solution we need some server-side based script reacting on the
> above given URL, which can evaluate the provided information and can create
> XML documents as given above.
>
> [1] http://wiki.services.**openoffice.org/wiki/Update_**
> Notification_Protocol<http://wiki.services.openoffice.org/wiki/Update_Notification_Protocol>
> [2] http://wiki.services.**openoffice.org/wiki/Update_**
> Notification_Protocol#summary_**information_about_request_to_.**
> 3CUpdateURL.3E<http://wiki.services.openoffice.org/wiki/Update_Notification_Protocol#summary_information_about_request_to_.3CUpdateURL.3E>
>
> I would prefer the "static" solution as a short-term one which could be
> working next week.
> For the "dynamic" solution a script is needed. I have no experience in
> programming such a script. Is there a volunteer who would take over this
> task?
>
>
> Any thoughts/comments/**improvements/changes/...?
>
>
> Best regards, Oliver.
>



-- 
----------------------------------------------------------------------------------------
MzK

"Well, life has a funny way of sneaking up on you
 And life has a funny way of helping you out
 Helping you out."
                            -- "Ironic", Alanis Morissette

--bcaec54b49d6a13ea304c02aa2a2--