[vlc-devel] Future of the update mechanism
remi at remlab.net
Thu Jul 30 18:53:47 CEST 2009
Le jeudi 30 juillet 2009 19:11:27 Dominique Leuenberger, vous avez écrit :
> The DNS way sounds very interesting, BUT this imposes the problem that
> you'd need to carry on the 'old' update list forever. A relatively
> ugly setup.
Why? You only need to track the "current" version for each platform.
> But on top of that suggestion, using a DNS TXT record could more or
> less serve what we look for:
> update TXT "<update><item os=windows version=1.0.1
> filename=vlc-1.0.1.exe link=http://www.videolan.org/mirroredlinkto.exe
> action=suggestDownload /><item os=openSUSE version=1.0.1
> link=http://www.videolan.org/suse/readme.html action=ShowReadme
TXT is cool. However, it is not an excuse to put bloated overly large XML.
Most annoyingly yet, there is no standard API to query anything but A and AAAA
More information about the vlc-devel