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 EF7D899FA for ; Wed, 28 Mar 2012 16:36:17 +0000 (UTC) Received: (qmail 28190 invoked by uid 500); 28 Mar 2012 16:36:17 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 28084 invoked by uid 500); 28 Mar 2012 16:36:17 -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 28074 invoked by uid 99); 28 Mar 2012 16:36:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Mar 2012 16:36:17 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 66.94.237.220 is neither permitted nor denied by domain of kay.schenk@gmail.com) Received: from [66.94.237.220] (HELO nm19.access.bullet.mail.mud.yahoo.com) (66.94.237.220) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 28 Mar 2012 16:36:07 +0000 Received: from [66.94.237.201] by nm19.access.bullet.mail.mud.yahoo.com with NNFMP; 28 Mar 2012 16:35:47 -0000 Received: from [98.139.221.48] by tm12.access.bullet.mail.mud.yahoo.com with NNFMP; 28 Mar 2012 16:35:47 -0000 Received: from [127.0.0.1] by smtp101.sbc.mail.bf1.yahoo.com with NNFMP; 28 Mar 2012 16:35:46 -0000 X-Yahoo-Newman-Id: 905999.45658.bm@smtp101.sbc.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: HhsYEmMVM1kjKwmdrWQrEjBdrfK0BA0l.KLWSnZNXMu2G1K k1iBzyugOJSgARmALKedxk0qPTUl4D9UNzvro3iet5ap6S2pjcgDwk0eTXJw n28wfMyaG_fyQSpFfRD7ZeF0kL.3GwXuIt02oOpo8L8VRjxpksuB2E6ykCC. Zikgw4atUgB0iiQjmkq.h8HMDKF9lL4ItX39weI2OQVdIoKAHgOz1RznXdiu wyNWKkbbfCY.vD6N5AndFDudmAKZBdF38R0wzp7qKN75c9VvX4Wc.Q.Rix4p MZuJW6BU.N9mHPwWnImbtGPiHAlohNnIG9iLGI1iTKNSWRcFuE4m8ZqBdsaY Hjskb2reqdY4c6Gr8LJ2MaebQQ.wbotlmzPoDmo4TrSIGQ1lGKw6dklGDTV8 uU1LTbP_s4xtMtxiZPjXabxwdooYWi1tXtor.8LtY23pCefZyGSwbwZKa.5A JkwXiC8TPFXbYf6dbJ79Y36sYLH5SUw.Of9Zgb626suqi3E3RoSDX1Tlc1fH p1ho- X-Yahoo-SMTP: dHt73eiswBAYjuZ6oL.TTjbe.KQkAIve Received: from [192.168.1.101] (kay.schenk@68.127.48.248 with plain) by smtp101.sbc.mail.bf1.yahoo.com with SMTP; 28 Mar 2012 09:35:46 -0700 PDT Message-ID: <4F733D10.40907@gmail.com> Date: Wed, 28 Mar 2012 09:32:16 -0700 From: Kay Schenk User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.27) Gecko/20120215 SUSE/3.1.19 Thunderbird/3.1.19 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: [DISCUSS][PROPOSAL] redirection of update services to www.openoffice.org References: <4F6C373F.20705@googlemail.com> In-Reply-To: <4F6C373F.20705@googlemail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 03/23/2012 01:41 AM, Oliver-Rainer Wittmann wrote: > Hi, > > On 22.03.2012 22:35, Kay Schenk wrote: >> As we all know, the program update services, the actual update equipment >> and the services they provided have not worked *in a while*, they are >> non-responsive. >> >> 1) Background and Problem >> >> This would include the following URLS: >> >> update.services.openoffice.org >> update30.services.openoffice.org >> update31.services.openoffice.org >> update32.services.openoffice.org >> update33.services.openoffice.org >> update34.services.openoffice.org >> update35.services.openoffice.org >> update36.services.openoffice.org >> >> Pings to these don't return. >> >> These are referenced in the program in a user's "install >> location"/program/"version init file" >> >> the name of "version init file" varies by installation platform. >> >> Each of the update services above typically included a check for update >> area with the name-- >> .../ProductUpdateService/check.Update >> >> A complete URL example (referenced in the version file): >> update36.services.openoffice.org/ProductUpdateService/check.Update(?"optional >> >> params") >> >> "check.Update" would normally be an xml feed which would include, as >> part >> of its entry for each platform, and language version, a pointer to >> another >> URL which would actually have and install the update for the given >> system. >> See details and notes on this at: >> >> http://wiki.services.openoffice.org/wiki/Update_Notification_Protocol >> >> >> 2) Proposed Solution >> Several participants on this list have been researching the "Update >> Notification Protocol" and creating "snippets" of the feeds (both simple >> and atom) for very limited one platform situations. However, the >> creation >> of a complete feed for all platforms has not been done ... yet. More >> research and development time is needed for this. >> >> Meanwhile, many current OOo users who either use the "check for updates" >> feature of their program or have updates "automatically enabled" >> continue >> to be frustrated with the unavailability of the update service. >> >> Although we still have not solved the problem of *HOW* to re-create the >> complete service (feed), we can create a "null" placeholder feed for all >> services mentioned in 1) that would return the message: >> >> "OpenOffice x.x is up to date" >> >> Essentially, all update services mentioned above would be redirected an >> appropriate area on the current web server, www.openoffice.org, which >> would >> return "no" information in placeholder feeds for each update service. >> >> >> Thoughts? >> >> >> > > First, Thx Kay for the summary. > > From my side a +1 to this proposal. > From my point of view the "no" information placeholder is a temporary > solution to fullfill the purpose to avoid the frustation of our users > of former versions. > It should be working until our AOO 3.4 release (may be 1 or 2 weeks > longer). > > When AOO 3.4 is out my expectation is that we provide a > platform-independent and language-independent "check.Update" > information which provides a download website which the user can open > in her/his browser from the office's update service dialog. On this > website we can state that AOO 3.4 is out and that the user should have > a look, if a corresponding package for her/his platform and language > is available for download and installation. > > Best regards, Oliver. After an "experiment" with just redirecting "update.services.openoffice.org", an older update service which I thought would have little impact, to www.openoffice.org yesterday, I am rescinding this suggestion. Yes, we need to port even a "simple" reply like this somewhere, but it's clear it can't be via the web server due to load considerations. Suggestions on an alternate setup/location? -- ------------------------------------------------------------------------ MzK "Women and cats will do as they please, and men and dogs should relax and get used to the idea." -- Robert Heinlein