I hthink the best way is to add a counter to the auth_user table or create a new table that references auth_user and you use for counting.
On Mar 22, 6:58 am, johntynan <jgty...@gmail.com> wrote: > Thankfully, I have received a decent amount of interest in the web2py > app that I've launched on Google App Engine here: > > http://opensourcebroadcasting.appspot.com/pledgedrives > > Now, my question is what is the best way to distinguish between Paid/ > Preferred users from people who are casually checking out the app. > > As it stands, all users can incur an unlimited of page views / > bandwidth / computing time (short of the billing threshold I've set up > within the app engine billing console). > > Would one approach be to have a session variable count the number of > page views per day across the entire app, and limit its use for unpaid > users? Could something like this be done without modifying the > table_user table? > > What are the best, proven approaches, that people have used to > differentiate casual users from people who have paid for a service > using web2py? > > Thanks kindly, JT -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
