Geo-Fencing
Users
There are 3 levels of privileges to an account who can use this feature.
- Normal: Statistics
- Content: Content Management (create/modify/delete groups, add/modify/delete files from the database and various groups)
- System: Create, modify and delete user accounts
Server
Database Tables
- policy (GroupID, GroupName SubnetIP, SubnetMask, City, Region, Country, StartTime, EndTime)
- group (GroupID, FileID)
- users (Username, Password, Type)
- Types: Normal(1), Content(2), System(3)
Client
The current monitoring client can be improved to include geo-fencing features as well. Following Screens could be a solution to handle the problem at hand.
- Authentication (Username, Password, Monitoring_Server_IP, Monitoring_Server_Port)
- Status (Running/Stopped, Start , Stop) (Optional: This can possibly be done if the server is running as service)
- Statistics
- (FileID -> P1, P2, ...)
- Connected Peers (Irrespective of whether they have a file or not)
- Content Management (create/modify/delete groups, add/modify/delete files from the database and various groups)
- User Accounts (Create/Modify/Delete account)
- Policy (GroupID, Groupname, SubnetIP, SubnetMask, City, Region, Country, StartTime, EndTime)
Points to consider
- How to resolve if there is any conflicting policy on a file or a group
