the project we are offereing is a windows based AVI (divx) style video on demand website with registered content to be served thru a web based and specifaclly designed player outside of winows/real player etc, the player will be designed to deliver content and data as say in 'athletics race' show footage with finishing order in XML file etc etc have something we can show should we need to.
From the player perspective, to answer your questions :
1) We’re aiming at using C as a platform. Why ?
1) more compact binaries (smaller download)
: 2) no need to install VB runtime libraries etc. Just download the program, and run.
. It will be designed to look similar to the “Windows XP?? desktop and media player.
Also, the player will be designed to support advertisements inside it if we want. It will be clickable, and fire up a browser instantly.
With respect to the website, the platform I have in mind is PHP + Apache. I propose this for a number of reasons.
: 1) Security risk of using Windows. There’s all sorts of nasties out there waiting for a publically accessible Windows host Anything from slammer, to the latest Blaster worm.
The website itself needs to do a number of functions:
: 1) to allow clients to access, and download the player
: 2) To be a community portal for all media to visit. Basically, we want to make it as attractive as possible to visit,
: 3) To allow clean, seamless uploads of the race footage and results by us or our appointed vendor
: 4) To allow clean tracking of video downloads both by us, as well as to offer an interface to the system for out content providers to check on status.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Installation package that will install the software (in ready-to-run condition) on the platform(s) specified in this bid request. 3) Complete ownership and distribution copyrights to all work purchased.
more info from above field:....
I propose The website will be developed using different panels for different bits of information. We use panels because they are easy to move around, and their content can either be automatically generated, fed from another source with our look and feel, or manually managed. Also, they can be managed independently
We still also need to design a database structure to support all this. One of the functionalities that the current player must have is for the user to select races by something other than date. With an appropriate database design, we can allow the user to search by name, by track, by any criteria… then they can queue the footage, and download. The new player will also need scheduling functionality they can set the videos that they want to download, and then schedule a time to download them (when they are sleeping, away from the computer etc.) The system should also cater for broken downloads. If they get cut off half way, the system does not deduct their credits. An administrative interface for managing users should be planned, with a complete history of when they logged on, from where, what they flagged to download, how long it took them, success/failure etc.