Database layer caching for video communications

1. A non-transitory, computer-readable medium encoded with instructions that, when executed by a computing device, cause the computing device to perform a method comprising:

receiving a Content Delivery Network (CDN) token key;

generating a message authentication code, at least in part based on the CDN token key and a content ID that identifies content within a webcast or a virtual event; and

transmitting event data including the content ID and the message authentication code.

2. The medium of claim 1 , the method further comprising:

generating a content hash, at least in part based on the content ID, wherein the message authentication code is generated, at least in part based further on the content hash.

3. The medium of claim 2 , wherein the content hash is generated, at least in part based further on a show identifier, a company key, and an event key, the show identifier is a randomized string, the company key identifies a tenant of the computing device, and the event key is associated with a presentation within an environment.

4. The medium of claim 3 , the method further comprising:

receiving an event registration indicating an event ID; and

determining the show identifier, the company key, and the event key, at least in part based on the event ID.

5. The medium of claim 2 , the method further comprising:

receiving a CDN content request including the content hash; and

transmitting the content, at least in part based on the CDN content request.

6. The medium of claim 1 , the method further comprising:

receiving an event registration that identifies a user ID for the webcast or virtual event, wherein the message authentication code is generated, at least in part based further on the user ID.

7. A computing device, comprising:

a network interface that receives a Content Delivery Network (CDN) token key and transmits event data including a content ID that identifies content within a webcast or a virtual event; and

a processor configured to generate a message authentication code, at least in part based on the content ID and the CDN token key, wherein

the event data further includes the message authentication code.

8. The computing device of claim 7 , wherein the processor is configured to generate a content hash, at least in part based on the content ID, and the message authentication code is generated, at least in part based further on the content hash.

9. The computing device of claim 8 , wherein the content hash is generated, at least in part based further on a show identifier, a company key, and an event key, the show identifier is a randomized string, the company key identifies a tenant of the computing device, and the event key is associated with a presentation within an environment.

10. The computing device of claim 9 , wherein the network interface receives an event registration indicating an event ID, and the processor is configured to determine the show identifier, the company key, and the event key, at least in part based on the event ID.

11. The computing device of claim 8 , wherein the network interface receives a CDN content request including the content hash, and the network interface transmits the content, at least in part based on the CDN content request.

12. The computing device of claim 7 , wherein the network interface receives an event registration that identifies a user ID for the webcast or virtual event, and the message authentication code is generated, at least in part based further on the user ID.

13. A method implemented by a host, the method comprising:

receiving a Content Delivery Network (CDN) token key;

generating a message authentication code, at least in part based on the CDN token key and a content ID that identifies content within a webcast or a virtual event; and

transmitting event data including the content ID and the message authentication code.

14. The method of claim 13 , further comprising:

generating a content hash, at least in part based on the content ID, wherein the message authentication code is generated, at least in part based further on the content hash.

15. The method of claim 14 , wherein the content hash is generated, at least in part based further on a show identifier, a company key, and an event key, the show identifier is a randomized string, the company key identifies a tenant of the host, and the event key is associated with a presentation within an environment.

16. The method of claim 15 , further comprising:

receiving an event registration indicating an event ID; and

determining the show identifier, the company key, and the event key, at least in part based on the event ID.

17. The method of claim 13 , further comprising:

receiving an event registration that identifies a user ID for the webcast or virtual event, wherein the message authentication code is generated, at least in part based further on the user ID.

18. The medium of claim 6 , the method further comprising:

generating a user value, at least in part based on the user ID; and

generating an access control list, at least in part based on the user value and the content ID, wherein the message authentication code is generated by hashing the access control list with the CDN token key.

19. The computing device of claim 12 , wherein the processor is configured to generate a user value, at least in part based on the user ID, and to generate an access control list, at least in part based on the user value and the content ID, and the message authentication code is generated by hashing the access control list with the CDN token key.

20. The method of claim 17 , further comprising:

generating a user value, at least in part based on the user ID; and

generating an access control list, at least in part based on the user value and the content ID, wherein the message authentication code is generated by hashing the access control list with the CDN token key.