You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment every web-client/browser needs access through firewalls/proxies to download the model using central from the original URL as well as to central.
Instead of that it would be possible that just the central-server is configured to access all necessary network-resources.
The client could just call an URL of the central-server and the server would stream the model-download to the client
This would open the door to some future improvements like:
Authentication/Authorisation of downloads managed by central. (OAuth-plugin, Kerberos-plugin)
central could be used as a Mirror or for Caching of remote models - similar to how Nexus can be configured when using maven. Nexus is used often this way for caching or to control which artifacts are used inside of a company.
uploading models with central without granting access for all web-clients to whatever storage central is using. so different storage strategies would be possible.
single point to configure firewall access. Would also be nice for cloud based services using models.
just a few ideas from a DevOp perspective
Will this change the current api? How?
Who will benefit from this enhancement?
References
list reference and related literature
list known implementations
The text was updated successfully, but these errors were encountered:
Description
At the moment every web-client/browser needs access through firewalls/proxies to download the model using central from the original URL as well as to central.
Instead of that it would be possible that just the central-server is configured to access all necessary network-resources.
The client could just call an URL of the central-server and the server would stream the model-download to the client
This would open the door to some future improvements like:
Authentication/Authorisation of downloads managed by central. (OAuth-plugin, Kerberos-plugin)
central could be used as a Mirror or for Caching of remote models - similar to how Nexus can be configured when using maven. Nexus is used often this way for caching or to control which artifacts are used inside of a company.
uploading models with central without granting access for all web-clients to whatever storage central is using. so different storage strategies would be possible.
single point to configure firewall access. Would also be nice for cloud based services using models.
just a few ideas from a DevOp perspective
Will this change the current api? How?
Who will benefit from this enhancement?
References
The text was updated successfully, but these errors were encountered: