Details
Improvement
Open
To be reviewed
Description
Version control applies to resources and components. What happens when one of those gets upgraded or their signature changes? There are several ways to handle this. Some discussion has taken place about this,. I expect this issue to be broken up into several sub issues at a later time.
Current thinking is along the line of
/resource/foo/1
/resource/foo/2
/resource/foo/LATEST
and so on.