This message was deleted.

A form of a lock table or TTL created with Device metadata

Do you have any reference or articles or architecture that can be followed

A locktable would just be a DB with a lock where the column name would be the device metadata tag (this could be IP-REGION-WIFI_NAME etc etc - anything that can be determined from the request metadata) For a request TTL/token, the first call to the Netflix server could create a token linked to the device metadata, and every subsequent request to the stream must have that token Different device = different token Could join the two

What if i am playing from multiple browser

I am sure it is more sophisticated than that But I would assume its related to device metadata linked to request metadata

I mean multiple tabs

Each tab would have a different init token Tie that token into your lock table, and only one can be active at a time

Hmm

Assuming netflix • Init stream request from Device creates a SessionToken • This Token is linked to a SessionTag which contains device/user/session metadata • A locktable is created which links that token to the metadata and is set to locked with a TTL on session init • On every subsequent (or new) request, the token must be present in the request, and the device/user/session metadata must match what is in the table • Should it not match, the request is rejected and the stream is dropped