Re: Enable choosing mirror for updates.xml (was: Re: Fwd: Update centers based on mirrors are a nightmare to support in an enterprise environment)

2021-06-03 Thread Matthias Bläsing
Hi, as there was _zero_ feedback, I just killed the experiment. I'll leave the code in the tools repository. Greetings Matthias Am Dienstag, dem 02.03.2021 um 20:08 +0100 schrieb Matthias Bläsing: > Hi, > > Am Donnerstag, den 30.01.2020, 14:55 + schrieb Jean-Marc Borer: > > > > This is

Enable choosing mirror for updates.xml (was: Re: Fwd: Update centers based on mirrors are a nightmare to support in an enterprise environment)

2021-03-02 Thread Matthias Bläsing
Hi, Am Donnerstag, den 30.01.2020, 14:55 + schrieb Jean-Marc Borer: > > This is bit of a complaint addressed to the NB infra community. When you > are stuck behind corporate proxy that is very aggressively filtering web > content, mirrors are a nightmare for you. In my case we need to

Re: Fwd: Update centers based on mirrors are a nightmare to support in an enterprise environment

2020-04-14 Thread Neil C Smith
Hi, On Tue, 14 Apr 2020 at 12:27, antonio wrote: > 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

Re: Fwd: Update centers based on mirrors are a nightmare to support in an enterprise environment

2020-04-14 Thread antonio
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

Re: Fwd: Update centers based on mirrors are a nightmare to support in an enterprise environment

2020-04-14 Thread Neil C Smith
On Tue, 14 Apr 2020 at 11:13, Matthias Bläsing wrote: > Yes - it is the _catalog_ not every nbm. Yes this still needs work (for > example instead of loading the catalog and working on the DOM, a > streaming parser should be able to do the modification on-the-fly). The > alternative would be to

Re: Fwd: Update centers based on mirrors are a nightmare to support in an enterprise environment

2020-04-14 Thread Matthias Bläsing
Am Dienstag, den 14.04.2020, 10:20 +0100 schrieb Neil C Smith: > On Mon, 13 Apr 2020 at 20:44, Matthias Bläsing > wrote: > > Fetch the base updates.xml: > ... > > The difference is, that the "distibution" attributes are relative i the > > base version and fully qualified in the mirror version. >

Re: Fwd: Update centers based on mirrors are a nightmare to support in an enterprise environment

2020-04-14 Thread Matthias Bläsing
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

Re: Fwd: Update centers based on mirrors are a nightmare to support in an enterprise environment

2020-04-14 Thread Neil C Smith
On Mon, 13 Apr 2020 at 20:44, Matthias Bläsing wrote: > Fetch the base updates.xml: ... > The difference is, that the "distibution" attributes are relative i the > base version and fully qualified in the mirror version. ... > Does this looks sane? If you're thinking of generating every request

Re: Fwd: Update centers based on mirrors are a nightmare to support in an enterprise environment

2020-04-13 Thread antonio
Hi Matthias, Sorry for the late reply. 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

Re: Fwd: Update centers based on mirrors are a nightmare to support in an enterprise environment

2020-04-13 Thread Matthias Bläsing
Hi all, Am Donnerstag, den 30.01.2020, 14:55 + schrieb Jean-Marc Borer: > This is bit of a complaint addressed to the NB infra community. When you > are stuck behind corporate proxy that is very aggressively filtering web > content, mirrors are a nightmare for you. In my case we need to

Fwd: Update centers based on mirrors are a nightmare to support in an enterprise environment

2020-01-30 Thread Jean-Marc Borer
Hi guys, This is bit of a complaint addressed to the NB infra community. When you are stuck behind corporate proxy that is very aggressively filtering web content, mirrors are a nightmare for you. In my case we need to whitelist every single server hosting java binaries otherwise we get empty