From 880103ca6d6b1835f03295d506f00de246210d4e Mon Sep 17 00:00:00 2001 From: Vimukthi Mayadunne <42222921+VimukthiMayadunne@users.noreply.github.com> Date: Mon, 20 Jan 2020 12:03:04 +0530 Subject: [PATCH] Updating proporsal 003 Minor changes --- ...ng_OAS_Definition_to_add_response_caching_for_an_API.md} | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename spec/proposals/{003_Extending_OAS_Definition_to_add_response_cashing_for_an_API.md => 003_Extending_OAS_Definition_to_add_response_caching_for_an_API.md} (86%) diff --git a/spec/proposals/003_Extending_OAS_Definition_to_add_response_cashing_for_an_API.md b/spec/proposals/003_Extending_OAS_Definition_to_add_response_caching_for_an_API.md similarity index 86% rename from spec/proposals/003_Extending_OAS_Definition_to_add_response_cashing_for_an_API.md rename to spec/proposals/003_Extending_OAS_Definition_to_add_response_caching_for_an_API.md index 9968f47..f5e2b10 100644 --- a/spec/proposals/003_Extending_OAS_Definition_to_add_response_cashing_for_an_API.md +++ b/spec/proposals/003_Extending_OAS_Definition_to_add_response_caching_for_an_API.md @@ -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| @@ -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