Welcome to Open Discussion
Status: Pre-Alpha
Brought to you by:
glassman1
Menu
▾
▴
Welcome to Open Discussion
Ok, it would be a cool feature to be able to "log in" and enter info about a person, say what kind of computer he uses, if they are on 24/7 and so. I am not sure how you people have though about the layout of the database, but Im sure it could be done in a rather nifty way to add some relations from email<->person, email<->ip, ip<->hardware platform and such.
Oh well, just some ideas.
/Bjorn
Yup, this is a great idea Bjorn. There was a pretty high demand (more than 2 emails requesting this) for the ability to have a "nickname" replace your email address in the stats where ever it shows up. We could create a second table that would be for such email lookups, the question is how does this get updated. The stats admin could do it via a perl script we provide, with the user how requested it sending the admin an email with the info. If you look how D.net does it, they have a big automated system that has passwords and web updates, etc. That is quite advanced, and probably beyond the scope of version 8.0 of ppstats.
Anyway, I like this and it should be done. I've been adding such things to the TODO list from the Bug Tracking forum. I'm not sure if the Bug Tracking forum in sourceforge is what this kind of thing was ment for, but its all setup to go. There is this other thing called Task Manager, but I haven't had time to see what it can do really. Any ideas?
One thing you *could* do would be to have kind of the same system dist.net uses, with a password thats mailed out to peoples email address, and they then uses that to log in and change theire information. Since v.8 runs on linux machines, everyone should have sendmail installed, so mailing shouldnt be a problem.
About the database design, it will probably be a bit slower to "chunk up" the data, but it would really clean up the table, and enable lots of other features, if we normalized it, atleast to BCNF (Boyce.Codd Normal Form). This way, we could have a table where each tuple (row) could contain for instance what machine the user is using, where he is from, what nickname he want to use, and so on. Another table could contain the blocks, with all the info about them, linked into the table with the user info as keys. You could then do the same with ip, and assing stuff to that, tho it could pose a problem when people use dial-up with non-static ips. But there is lot of stuff you can do this way. You can store the country and the name of the flags in one table, OS'es and theire icons on another and so on. This shouldnt complicate neither the insertion nor the SQL queries, but it does enable us to have some nifty features. And its a correct use of a relational database ;)
/Bjorn
Ofcourse, the cached DNS could also be done in a table, which would speed up the resolving time if it can be done in an indexed table.
I'm doing something similar to this for the team I'm on. Basically I have 3 tables right now (but it can be easily expanded).
1. the log files get loaded into one table
2. user information table -- stores user names, country, dnet id, personal webpage. Has the potential to store more information.
3. and email -> userid table -- holds what email addresses belong to what username (you can have multiple email addresses per each userid) and has a flag for whether or not a particular email address is a member of the team.
All the country, cpu, and os data is stored in an arrays. (I don't know if they would be better in their own tables or not)
Information which could easily be added:
4. ip table - information on what ip submitted what blocks, what emails/users are submitting from what ip/hostname
5. computer table (?) - users could enter information about what computers they are running, and what the benchmarked results are.
The pages are here:
http://mika.dhs.org/rc5/anandtech/
Take a look within the code in this file:
http://www.intrepid.de/ppstats/ppstats-8.1-alpha-5.tar.gz
This is a version made from the CVS-8.0 that supports MySQL as DB instead of the perl-arrays.
For the stats I have. I have a users table and a blocks table. When the first blocks are received from a new user. It geterates the account in the user table with a random 6 character password.
When selecting from the database. I select from both tables at once.
eg. SELECT u.Name,u.Flag,SUM(Blocks) FROM Users u,Blocks b WHERE u.Email = b.Email
So now they have there own personalized name and flag.
Hi Mika! nice to see an AnandTecher here.
anyway, i see this place moves really slowly, but for anyone interested, here is a link to the working Team AnandTech page:
http://www.teamanandtech.com/dent
it has nifty features, and uses ppstats71
BTW, why is this place so dead?
Because there isn't much life in the group (most of us are old geezers with jobs)... :)