Page 1 of 1
Limiting bandwidth not content
Posted:
November 22nd, 2011, 8:03 am
by mmuldoon
Hey guys I did a quick search of the board and didn't find anything like this. Instead of limiting content per subscription level, I would like to limit bandwidth per subscription level. I run
http://www.blendswap.com where we have 3d models to download but we've had to enact a bandwidth limit of 100mb a week for users to help our server costs. So basically we need a membership plugin that can be made to limit mb/downloads. Would it be possible to get S2 to work this way?
Thanks for your help.
Re: Limiting bandwidth not content
Posted:
November 25th, 2011, 11:32 pm
by Cristián Lávaque
Have you already tried using a cheap hosting for files like Amazon S3?
Re: Limiting bandwidth not content
Posted:
November 26th, 2011, 5:31 pm
by mmuldoon
No we haven't we would like to keep the files on our server and then just have a member ship plugin that would handle the monthly payments and set rules for what amount of bandwidth is received depending on the membership tier.
Re: Limiting bandwidth not content
Posted:
November 28th, 2011, 10:05 am
by mmuldoon
Anyone know if this is possible? Or do I need to hire it out. Need an answer pretty quick.
Thanks
Re: Limiting bandwidth not content
Posted:
November 29th, 2011, 1:26 am
by Cristián Lávaque
I know s2Member doesn't manage file downloads based on bandwidth.
I don't know if it's possible. If this were calculated based on the file's size, what happens if the transfer fails? What happens if the guy is just resuming a broken download? Neither of those cases could be calculated from the file's size. You could probably stream the file via your script, but I don't know if this would keep count of the data transfered to know the exact bandwidth used.
You could post this job in a freelance site like oDesk or eLance, see if someone bids on it and says it can be done.
I hope it helps.
Re: Limiting bandwidth not content
Posted:
December 5th, 2011, 3:01 pm
by mmuldoon
Ok how about this, what we need is to update a little meta field for each user depending on what the value is for each user, the site reads that and responds the payments plug just needs to set up that field.