We apologize for the instability of composr.app and appreciate your patience. We are working on the statistics addon and trying to find an optimal way to store and render data. Unfortunately, we have yet to find a solution that can handle the traffic (and therefore, tens of millions of statistical records) of composr.app. We're working hard on one.
This should just be done using a firewall or .htaccess rules.
Building it into Composr is too problem-filled. If someone would understand the complexities, they'd be most comfortable doing it at the web server level anyway.
Use cases:
- Security on high-access accounts
- Intranet security (matching to specific machines)
- Prevent multiple-registrations
Caveats:
- Proxies
- Shared machines / public machines
- Mobile IPs very dynamic
- DHCP in general
- Proxies
Full discussion:
http://compo.sr/forum/topicview/misc/deploying/points-awarded-before.htm?post_id=108423&keep_refreshed_once=1#post_108423
Building it into Composr is too problem-filled. If someone would understand the complexities, they'd be most comfortable doing it at the web server level anyway.