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
{{ message }}
This repository has been archived by the owner on Nov 21, 2018. It is now read-only.
Currently, there's no way to retrieve information about the service being interacted with (e.g., its name).
This would be useful in some cases like error reporting (i.e., which service is having an issue?).
I'm thinking we create a ResterMetaData middleware that looks for paths beginning in /rester/v* and processes them. For example, /rester/v1/info could return a hash of information about the service (i.e., {"name": "MyService", "versions": [2,3,4]})
In the future, we could use this for more advanced things too. For example, retrieving a list of available endpoints (/rester/v1/endpoints) or getting details on endpoints (/rester/v1/endpoints/v3/users -- could return required parameters).
The version in /rester/v1/info would allow us to support different versions of the builtin metadata endpoints.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, there's no way to retrieve information about the service being interacted with (e.g., its name).
This would be useful in some cases like error reporting (i.e., which service is having an issue?).
I'm thinking we create a
ResterMetaData
middleware that looks for paths beginning in/rester/v*
and processes them. For example,/rester/v1/info
could return a hash of information about the service (i.e.,{"name": "MyService", "versions": [2,3,4]}
)In the future, we could use this for more advanced things too. For example, retrieving a list of available endpoints (
/rester/v1/endpoints
) or getting details on endpoints (/rester/v1/endpoints/v3/users
-- could return required parameters).The version in
/rester/v1/info
would allow us to support different versions of the builtin metadata endpoints.The text was updated successfully, but these errors were encountered: