Describe the request
The Pharo Launcher is getting all the template lists and all the information from querying different servers. It is doing it once per session of the launcher. It should use the HEAD operation in the HTTP protocol to detect if a resource has been modified since the last request. If the resource has not been modified it should use the cache one. As described in the HTTP protocol in
https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/HEAD
Expected behavior
Pharo Launcher uses correctly the HTTP support for caching resources and the life of the cached resources. This will improve the network usage and the dependency on having correct connection all the time.
Expected development cost
It requires improving all the requests adding first a HEAD request and then the GET operation. This can be handled in a single component to do the request but requires to change all the users of the network operations.
Describe the request The Pharo Launcher is getting all the template lists and all the information from querying different servers. It is doing it once per session of the launcher. It should use the HEAD operation in the HTTP protocol to detect if a resource has been modified since the last request. If the resource has not been modified it should use the cache one. As described in the HTTP protocol in https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/HEAD
Expected behavior Pharo Launcher uses correctly the HTTP support for caching resources and the life of the cached resources. This will improve the network usage and the dependency on having correct connection all the time.
Expected development cost It requires improving all the requests adding first a HEAD request and then the GET operation. This can be handled in a single component to do the request but requires to change all the users of the network operations.
Version information: