Forum

Pay-per-view: Limit client to specified maximum concurrent connections or bandwidth

Jacques Snyman 2015-04-14 09:51:46 UTC in Paywall: WMSAuth and beyond

Is there any way we can limit a client (authorised by PPV handler) to only a specified maximum number of concurrent connections or maybe limit the amount of bandwith available to that specific client?

Alex Pokotilo 2015-04-14 10:26:45 UTC 

if you authenticate your clients and can assign unique IDs to your clients you can check how many streams each unique clients view and stop signing urls for your clients. Nimble cannot distinguish one client from another and your web site need to use login information for given client to assign client's id appropriately so that based on that id you can check how many streams client currently watch and block it temparary if limit exceed

Jacques Snyman 2015-04-14 10:43:02 UTC 

Thats what I thought, yes... the only issue I'm dealing with is, how do I know (from the website) when a client has closed their connection (stopped vieing the stream), so that I can allow subsequent connections again?

Alex Pokotilo 2015-04-14 12:00:27 UTC 

you will see clients disconnect in ppv handler

Jacques Snyman 2015-04-14 12:10:53 UTC 

Perfect. Thanks

Paul 2016-03-09 14:17:24 UTC 

Jacques, please can you help me.

Do you have any working PPV code examples I could see for the PPV?

I have not done PHP/MySQL etc in many years and it will take me a long time to get this working.

It would be a great help if you have any pages/code that shows how to integrate with database to see if user has paid / has membership or not.

I have seen the basic examples on github but for me to go from that to a full working system will be a very difficult task.

Thank you

Yury Udovichenko 2016-03-09 23:38:37 UTC 
Paul 2016-03-10 11:42:36 UTC 

Thanks, had not seen the first guide with the database queries.

Hopefully that will help me.

Post a reply


Post a new question

Categories:

This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the Privacy Policy. If you want to know more or withdraw your consent to all or some of the cookies, please refer to the Privacy Policy.
By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies.