Timeline for Handling multiple rest api versions within Android Java client
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 3, 2016 at 12:33 | comment | added | Pedro Teran | that's exactly what I've said before, but they need to extend some functionality not present on api v1 that is present on api v2 but have to maintain backward compatibility. and also moving everything to api v2 is not an option directly since some clients have server with api v1 only and they don't want to force them to update | |
| Feb 2, 2016 at 21:53 | comment | added | RubberChickenLeader | have you thought about API Versioning? original API stays the same while the new api is at something like site.com/api/V2/endpoint. Old app and new app live happily together for a while (until you kill V1) | |
| Feb 2, 2016 at 19:44 | history | edited | gnat | CC BY-SA 3.0 | spelling cleanup |
| Feb 2, 2016 at 19:43 | review | First posts | |||
| Feb 9, 2016 at 6:14 | |||||
| Feb 2, 2016 at 19:41 | history | asked | Pedro Teran | CC BY-SA 3.0 |