Feature #2417
REST path using file extension
| Status: | New | Start date: | 11/11/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | harlo | % Done: | 0% | |
| Category: | - | |||
| Target version: | InformaCam - SERVER v2 | |||
| Component: |
Description
From a REST perspect, this would be a better path structure (using a file type extension)
https://j3m.info/submission/a4280ff24ae58f5fa2c23d146e7bde94.j3m
you could then support access to other data from the submission such as:
https://j3m.info/submission/a4280ff24ae58f5fa2c23d146e7bde94.jpg
https://j3m.info/submission/a4280ff24ae58f5fa2c23d146e7bde94.mkv
https://j3m.info/submission/a4280ff24ae58f5fa2c23d146e7bde94.gpg (public signature)
https://j3m.info/submission/a4280ff24ae58f5fa2c23d146e7bde94.html (download HTML report)
https://j3m.info/submission/a4280ff24ae58f5fa2c23d146e7bde94.txt (simple plain text readout of j3m)
and so on.
a path like this, while the difference is subtle:
https://j3m.info/submission/a4280ff24ae58f5fa2c23d146e7bde94/j3m/
to me means you are accessing a different resource, not a different format from the same identifier.