On 2016-05-24 08:42, Sönke Ludwig wrote:

Since fetching dependencies usually saturates the network connection,
that wouldn't save much time (or do you just mean fetching the package
recipes in parallel?).


No, I mean fetching the full package in parallel.

But because it also requires full dependency
resolution, it would have a considerable impact on server load.

Does it really take that much resources?

And of course that would make it impossible to use a simple file server as a
package registry.

How important is that? The client could first try the API call to give the full set of dependencies, if that fail, fallback to the current approach.

--
/Jacob Carlborg

Reply via email to