-
Notifications
You must be signed in to change notification settings - Fork 436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable a more efficient polling of catalog #529
Comments
Most of our brokers use a static catalog, so it is not an issue on the broker side. It would be nice if a broker could specify the period when the platform should refresh the catalog, e.g. via |
@mattmcneeney was this discussed during the call this week? Any feedback? |
I'm not sure what an etag is exactly, but I agree with the goal described
here
…On Tue, Jun 19, 2018 at 3:49 PM, Doug Davis ***@***.***> wrote:
@mattmcneeney <https://github.com/mattmcneeney> was this discussed during
the call this week? Any feedback?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#529 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAWXmDdKSeEYnprp7BrTOg5pIEa8ib_Iks5t-VXjgaJpZM4UnTXu>
.
|
While true its part of the HTTP spec, given not everyone knows about it (as shown by Paul's comment), I suspect that unless we call it out people will not consider supporting this optional feature. So, a PR on this wouldn't require people to use it, but rather make people aware of it and explain any implications of its use. I know that some uses of OSBAPI will ping the catalog quite often, so I think highlighting this to help performance would be nice. |
@jberkhahn is this still something that may be of use to the svc-cat community? |
sure |
@jberkhahn Cool - do you want to own opening the PR for this one? :) |
i'll try to get around to it this week |
What do people think about supporting an ETag type of mechanism for /v2/catalog so that a broker can return "304 Not Modified" if nothing has changed since the last time the Platform queried the catalog? It would save the broker the time of regenerating the result, and it will save the platform the time of diff'ing it.
The text was updated successfully, but these errors were encountered: