Custom reference tag for versioning
A resource host transmits a payload to a client device. The payload includes a first asset hosted by the resource host, and the first asset is associated with a first reference tag indicating a versioning status of the first asset. The resource host receives an Add Ref Instruction, wherein the Add Ref Instruction, which includes a custom reference tag indicating a user-selected versioning status of the first asset. The resource host associates a second reference tag with the first asset based on the custom reference tag.
1. A method comprising:
transmitting a payload from a resource host to a client device, wherein the payload includes a first asset hosted by the resource host, and wherein the first asset is associated with a first reference tag indicating a versioning status of the first asset;
receiving, at the resource host, an Add Ref Instruction, wherein the Add Ref Instruction includes a custom reference tag indicating a user-selected versioning status of the first asset;
associating a second reference tag with the first asset based on the custom reference tag; and
generating an identifier of a second asset based on a hash of the second asset.
2. The method of claim 1 , wherein:
the custom reference tag indicates that the user-selected versioning status indicates that the first asset is an un-versioned resource.
3. The method of claim 1 , wherein transmitting the payload from the resource host to the client device includes:
transmitting the payload from the resource host to a proxy device; and re-transmitting the payload from the proxy device to the client device.
4. The method of claim 1 , further comprising:
receiving a modified version of the first asset at the resource host, wherein the modified version of the first asset is transmitted from the client device to the resource host.
5. The method of claim 4 , further comprising:
storing the modified version of the first asset as the second asset at the resource host; and associating, by the resource host, the second reference tag with the second asset.
6. The method of claim 1 , wherein:
the resource host receives the Add Ref instruction directly from the client device.
7. A resource host comprising:
a processor;
memory coupled to the processor, the memory configured to store hosted assets;
a communications interface coupled to the processor and the memory, wherein
the communications interface is configured to:
transmit a payload from the resource host to a client device, and wherein:
the payload includes a first asset hosted by the resource host;
the first asset is associated with a first reference tag indicating a versioning status of the first asset;
receive an Add Ref Instruction, wherein the Add Ref Instruction includes a custom reference tag indicating a user-selected versioning status of the first asset;
the processor is configured to:
associate a second reference tag with the first asset based on the custom reference tag; and
generate an identifier of a second asset based on a hash of the second asset.
8. The resource host of claim 7 , wherein:
the custom reference tag indicates that the user-selected versioning status indicates that the first asset is an un-versioned resource.
9. The resource host of claim 7 , wherein the communications interface is further configured to:
transmit the payload from the resource host to a proxy device.
10. The resource host of claim 7 , wherein the communications interface is further configured to:
receive a modified version of the first asset at the resource host, wherein the modified version of the first asset is transmitted from the client device to the resource host.
11. The resource host of claim 10 , wherein:
the memory is further configured to store the modified version of the first asset as the second asset; and
the processor is further configured to associate the second reference tag with the second asset.
12. The resource host of claim 7 , wherein the communications interface is further configured to:
receive the Add Ref instruction directly from the client device.
13. A non-transitory computer readable medium tangibly embodying a program of instructions stored in a memory and executed by a processor, the program of instructions comprising:
at least one instruction to transmit a payload from a resource host to a client device, wherein the payload includes a first asset hosted by the resource host, and wherein the first asset is associated with a first reference tag indicating a versioning status of the first asset;
at least one instruction to receive, at the resource host, an Add Ref Instruction, wherein the Add Ref Instruction includes a custom reference tag indicating a user-selected versioning status of the first asset;
at least one instruction to associate a second reference tag with the first asset based on the custom reference tag; and
at least one instruction to generate an identifier of a second asset based on a hash of the second asset.
14. The non-transitory computer readable medium of claim 13 , wherein:
the custom reference tag indicates that the user-selected versioning status indicates that the first asset is an un-versioned resource.
15. The non-transitory computer readable medium of claim 13 , wherein
the at least one instruction to transmit the payload from the resource host to the client device includes: at least one instruction to transmit the payload from the resource host to a proxy device.
16. The non-transitory computer readable medium of claim 13 , further comprising: at least one instruction to receive a modified version of the first asset at the resource host, wherein the modified version of the first asset is transmitted from the client device to the resource host.
17. The non-transitory computer readable medium of claim 16 , further comprising:
at least one instruction to store the modified version of the first asset as the second asset at the resource host; and
at least one instruction to associate, by the resource host, the second reference tag with the second asset.