Hi Matthias,
Thanks for the explanation, crystal clear now.
I think it's better to generate an "update.xml" file for each mirror,
containing full urls for the given mirror, and generate them _once_, and
not for _every_ user request. That would be 226 [1] update-xml files. We
can generate a webpage that allows users to select a mirror of their choice.
Then Jean-Marc can download this mirror-specific update.xml file (for
the mirror of their IT dept. choice), add it to his update center in the
IDE, and download files directly from that mirror.
Would this work?
Regarding the "fragile update code" I think we should think about a more
Apache-centric solution to the problem, and refactor/review the code,
right? Maybe 13.0 is a good target?
Kind regards,
Antonio
[1]
http://www.apache.org/mirrors/dist.html
Currently there're 226 Apache full mirrors.
El 14/4/20 a las 11:59, Matthias Bläsing escribió:
Hi,
Am Dienstag, den 14.04.2020, 06:02 +0200 schrieb antonio:
I see your point, I just can't understand why this computes the URLs on
the server side (in the netbeans-vm php file) and not on the client side
(in the IDE itself).
Wouldn't it be easier to let the user choose her preferred mirror(from a
drop down list, for example) and then compute the appropriate URLs from
that? I have a limited understanding on the internals of the update
center logic, so I usually get lost on this.
ok, the problem is this:
updates.xml is our trust anchor. It must come from a trusted source
(apache infrastructure) and that is not the case for the mirror
network.
In the updates.xml the URLs to location to the nbms is specified
relative to the location of the updates.xml file.
This is where the current redirection magic comes in. When nbms are
requested the request is passed through a redirect cascade, that ends
in closer.lua, which redirects the request to the "right" mirror.
The problem is:
a) the right mirror can't be found when requested via IPv6
b) the right mirror sometimes needs to be one specific mirror
c) if the users location can't be determined "preferred" in closer.lua
is ignored
So instead of relying on closer.lua the script moves the decision to
the user. Who can specify the mirror to use via the `mirror` parameter.
The PHP script modifies the XML structure to hold absolute URLs instead
of relative ones.
This could be moved to the Netbeans Code, but then the already fragile
autoupdate code would need a special case just to deal with the
speciality of the apache infrastructure. We saw in the past, that
nearly nobody is willing to go into the autoupdate code and I don't see
this changing anytime soon.
It would still be helpful to create the right URL in the IDE, but
without the server support, this won't fly.
Greetings
Matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
