Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Date: Fri, 27 Jan 2012 10:05:54 -0300
From: Ariel Constenla-Haile <arielch@apache.org>
To: ooo-dev@incubator.apache.org
Subject: Re: [CODE] update services
Message-ID: <20120127130554.GA5730@localhost>
References: <20120125203400.GB22542@localhost>
 <CAGj3216Lb9X+S9czviF6QN5YgR8=+NMgd+6EqwQY42PgJ68TsQ@mail.gmail.com>
 <4F20A81A.6000806@cfl.rr.com>
 <C67A81EF-E53E-414C-831F-F71278F2312E@comcast.net>
 <21FC7F6C-7C42-44EA-98E5-3FF57D5DC4BF@comcast.net>
 <1327594498.52092.YahooMailNeo@web160902.mail.bf1.yahoo.com>
 <CAGj3216WDC=aJAGN1aedCNoCFAqRtjmeUgOn6Psfqf6T8iuYug@mail.gmail.com>
 <CAGj3215iy+0RY3HeRA+_TjR_fvTvTdD4dr3QksbUianiMd7giA@mail.gmail.com>
 <20120127010233.GB4872@localhost>
 <4F225AB9.5070105@apache.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="9amGYk9869ThD9tj"
Content-Disposition: inline
In-Reply-To: <4F225AB9.5070105@apache.org>
User-Agent: Mutt/1.5.21 (2010-09-15)

--9amGYk9869ThD9tj
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Andrea, Regina, *,


On Fri, Jan 27, 2012 at 09:05:13AM +0100, Andrea Pescetti wrote:
> On 27/01/2012 Ariel Constenla-Haile wrote:
> >the information must be out there, we just have to research, and study
> >the code. An example searching the wiki:
> >http://wiki.services.openoffice.org/wiki/Update_Notification_Protocol
> >IMO we are far from being out of luck :)
>=20
> We've already discussed that page, but at first glance it seems the
> specification of a further version of the update protocol, and I'm
> not sure it was ever implemented.

this is actually implemented.
I pointed OOO320m18 (Build:9502) to
http://people.apache.org/~arielch/ProductUpdateService/check.Update.feed

and I got
http://people.apache.org/~arielch/ProductUpdateService/update_success.png
http://people.apache.org/~arielch/ProductUpdateService/update_download.png

>=20
> However, what the service does is merely serving a "Yes" (updates
> available) or "No", so, as elaborate as it can be, it shouldn't be
> impossible to replicate it in a way that always answers "No" until
> Apache OpenOffice 3.4 is out and always answers "Yes" when Apache
> OpenOffice 3.4 is available (Apache OpenOffice 3.4 can point to
> another URL, so it won't happen that people already using Apache
> OpenOffice 3.4 get erroneous messages about available updates).


a dummy
http://people.apache.org/~arielch/ProductUpdateService/check.Update
will indicate every OOo version that it is up-to-date (we may not want
this - an OOo 3.2 will not be seen as un update to an OOo 3.1, for
example).

Unfortunately I cannot test how this is implemented because the feature
depends on functionality removed in the IP clearance (libneon), and
I don't have a pre-ip-clearance build to test.


Regards
--=20
Ariel Constenla-Haile
La Plata, Argentina

--9amGYk9869ThD9tj
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJPIqEyAAoJEMjP1bm45QNWPrAP/RLoffWSIPJeHhYCWw8brJVe
tC4hnC9zhu+Q4PKfIwWc74lgyc0PIkd61FeO/4Pvs11/ukkbYQgtevt631qyPH2/
k9woU9ymVIsqjoxJ4H4ThBVvfG4gQAYi8jHbXQ2g8NNzLY+9JIvTuLnKK2FhSJS6
RTTnaz+iEokodqZp7s46t9ocxkWzoaOZwxndjbX6PGZjsMfmroRRsfQN91PWUG28
2Xrvae9FvL1hFYSs91xMirlSDAGx9WvzKphzhmvlJX28SDd3hMA0fitQgdMDU2Im
vJw7ymJe0jr1/R9t+0gUatc5EwRGwqrdqM+GnWjP19251ifJkhPEGPwfUiIiuISx
RsGR5FqcDDqYSoQqeeM7IAmH9whiC4lshG440UuMTToog4cnjAMHQ3rG0NQV11Y6
vg8olHv/p2WBpRmCCg9DA8qCONo3BAdd+gwzB45/8hs9G0rr7jpyBn465/ZRJq7M
TfFaQSGlTiG//oL0xax5OwdhUCsa+DvInGhurhQFbIu5NASeMIuy5MG3grx6aVVO
FSOKuYFSrnTYNflvJY3f/aZOeTrTFwDz2OW8VGYEte8CuVWGcLNI5RwPeAZeeCJB
aiXHTxpW4ku6kUOCyJO43bTtEToUWO2WEbsupUleC+V7TIf7WxY19pdKAcNb9r0C
Jy0H9PSfvFA3J8bfEIq5
=ioWs
-----END PGP SIGNATURE-----

--9amGYk9869ThD9tj--