db0@lemmy.dbzer0.com to Programmer Humor@programming.dev · 2 days agoThat shadowy placelemmy.dbzer0.comimagemessage-square40fedilinkarrow-up1969arrow-down10
arrow-up1969arrow-down1imageThat shadowy placelemmy.dbzer0.comdb0@lemmy.dbzer0.com to Programmer Humor@programming.dev · 2 days agomessage-square40fedilink
minus-squareLongpork3@lemmy.nzlinkfedilinkarrow-up2arrow-down1·2 days agoA translation layer could be used, no? Check api version, translate any v1 specific calls into their v2 counterparts, then submit the v2 request?
minus-squareCosmicTurtle0@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up2·1 day agoThis isn’t really efficient because when v2 gets updated now you have to update the translation layer as well. Any improvements you made in v2 would likely not translate. Essentially the best way is to provide users with an incentive to switch. Perhaps a new feature or more requests.
minus-squarePieisawesome@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up1·9 hours agoPublish v3, then add a translation layer for v2 to v3
A translation layer could be used, no? Check api version, translate any v1 specific calls into their v2 counterparts, then submit the v2 request?
This isn’t really efficient because when v2 gets updated now you have to update the translation layer as well.
Any improvements you made in v2 would likely not translate.
Essentially the best way is to provide users with an incentive to switch. Perhaps a new feature or more requests.
Publish v3, then add a translation layer for v2 to v3