24744 dynamic HTML document creation

Introduction This is an Internet based application will be using Apache (Apache-SSL for the production server), MySQL and PHP technologies. The HFA website provides HTTP document is based on user identity after the source server that is serving the user request is also authenticated. The Network Environment The HFA server is an independent computer(s) running web server, Database and PHP software. The Source Server is third party application server, also running a set of software applications (web server, Database and other dynamic content pre-processor) that is serving customer request. The user requesting service is using a computer terminal that is connected to the network with HTML capable client software. All computers are communicating with each other over a TCP/IP connection. Operation requirements The HFA server Accept connection request from the Source Server After verifies the Source Server id, Client Session id, Client Session state and the User id. It will return a validation status plus a HTML document on validation. The dynamic HTML document generated by HFA server will be delivered to the source server, being part of the HTML document requested by the user. Every HTML document is generated according to the validated user profile/preference that has been registered with the HFA server and in accordance with the document category requested by the source server. The HFA server shall always signal the source server whether the user id is validated and execute a server side script or shell program and store the result along with the session information. And a default document will be returned if invalid user id or invalid session id is detected. The dynamic HTML document contains array of randomly selected visual, audible objects or other form of multimedia objects with at least one of the object is the type that meets the user profile/preference. The document will include other HTML comparable objects including JavaScript that is retrieved from the database. HFA server shall be keeping a temporary register of sessions and clean out the session when it has timed out. HFA server will be required to validate user id based on HTTP command information with the data already stored in its register, generated when a valid request is make from the source server with a proprietary protocol. (The socket based user id validation solution will be developed after the completion of current project). In addition to retrieving images/icons from the database table, capability to create dynamic graphical icons with alphanumeric characters shall be investigated – such as advanced version CAPTHA will be welcome. Upload facility to enable user upload small file to the database and save to the appropriate table based on the file type and category (must carry out virus scan on the received file, before it is stored to the database) Capture live recording or audio/video from client side microphone/video camera. (Optional feature) User registration, user profile maintenancs web pages Template based web site design allowing the service to be customised in later date