Skip to content
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.

Sign up for GitHub

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

Updating proporsal 003 #6

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Updating proporsal 003 #6

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions ...ion_to_add_response_cashing_for_an_API.md → ...ion_to_add_response_caching_for_an_API.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
# Extending OAS Definition to add response cashing for an API
# Extending OAS Definition to add response caching for an API

## Metadata

|Tag |Value |
|---- | ---------------- |
|Proposal |[001]()|
|Authors|[Vimukthi Mayadunne](https://github.com/VimukthiMayadunne), [Author 2](https://github.com/{author2})|
|Authors|[Vimukthi Mayadunne](https://github.com/VimukthiMayadunne)|
|Review Manager |TBD |
|Status |Proposal|

Expand All @@ -20,7 +20,7 @@
This feature can be used to define caching responses received from a backend in the api-gateway.

## Motivation
This feature will help the API developers to provide the necessary configurations required for apply response chasing functionalities to an api-gateway and to invoke response cashing just by providing that in the swagger/OAS definition rather than applying response cashing to an API in the gateway via API gateway -UI (AKA Publisher U.I.) or other methods .This will make response chasing configurations more human readable as well.
This feature will help the API developers to provide the necessary configurations required for apply response caching functionalities to an api-gateway and to invoke response caching just by providing that in the swagger/OAS definition rather than applying response caching to an API in the gateway via API gateway -UI (AKA Publisher U.I.) or other methods .This will make response caching configurations more human readable as well.

## Proposed solution
Proposed solution is to add an extension to the OAS spec where that extension describes the following attributes
Expand Down