By modifying the in the flows to include a parameter to replace the version number, it allows for flexibility in managing different versions of the API
Hmm, I don't know. I feel like all these options are kinda messy. Why don't we just use a versioning strategy that's already been battle-tested, like the one used by the major cloud providers? That way, we don't have to reinvent the wheel.
Hmm, let me think about this... I think option C might be the way to go. Modifying the baseURI to include a variable for the version number sounds like a good way to expose multiple versions of the same API.
Alesia
10 months agoTawna
10 months agoAnjelica
10 months agoMagda
10 months agoTawna
10 months agoRene
10 months agoJoanna
10 months agoRene
10 months agoStefania
10 months agoJoanna
11 months agoStefania
12 months agoNan
12 months agoNicholle
11 months agoRonnie
11 months agoVirgie
1 years agoJulieta
1 years ago