First off - i don't profess to know it all about this, and i will be asking to people to add points but i'd like to keep this as clean of comments as possible so please respond with ideas thoughts to this thread...
http://forums.hexus.net/showthread.php?t=20024
Right you need a front end to a VEF replacement.
1) My thoughts on this based on my experiences are to remove the choice of mission and auto generate the lot.
Reasons for this is based on a few things - people then can't get their choice of plane, remove the BF110C issue with OKL and try and make the plane use based on more historical figures.
Plus technically it makes it easier to manage.
2) so you have a web site - do you need to have logins?? surely this is governed by Hyperlobby log in?, or is it?, i've not seen any reason to have a login on the VEF site.
Track based on Pilots reported in missions, Those that don't fly within 1 month of last reported mission will just be dropped from the database.
3) So mission generation would have to be similar to VEF, you want to host then you have to enter a part of the sight and it will down load you a mission. Some form of user Identification would be used here as reports of bad hosting cheating etc etc would result in a bad from being able to host.
I want to host a mission i get auto generated file. Hosts must be responsible enough to only request missions when intending to fly them.
4) Mission generation believe it or not is probably pretty easy.
I could write the text file myself using a database generated system, or as the case seems use DGen or even replace it with something liek this...
http://www.lowengrin.com/content.php?article.12
5) mission reports happen same way as they do now, upload of co-op.txt - which then parses the results and inputs onto the database to allow querying on.
Technicals to follow of how to do this?.