3 ms·
This doesn't seem like a particularly scalable solution, since your traffic increases proportionally to the number of versions you support.
by abrichr 13y ago
This doesn't seem like a particularly scalable solution, since your traffic increases proportionally to the number of versions you support.
- arethuza 13y agoI would suggest that if it works for Salesforce then it probably does scale...
- abrichr 13y agoPerhaps, but I would prefer to see some evidence rather than rely on an appeal to authority. If the size of your resource is e.g. 100KB, and you have 10 different versions, then your responses are 1MB each -- 9 times larger than they have to be. This can result in significant bandwidth costs, depending on your number of users and their behaviour.
- arethuza 13y agoI think you are misunderstanding how it works - you don't get every possible response format, that would indeed be silly. You get the response type specific to that version of the interface - which is pretty normal versioning. All I was saying is that if you do run multiple versions of the same interface on different URLs then it's quite nice to have these versions themselves treated as resources you can find out about through the interface. That's what Salesforce do and, in my experience, I think it is simple and elegant.
- abrichr 13y agoAh, now I understand. Yes, I agree that discoverability is an extremely useful feature.