last remark regarding the previous remark :: one importan remark regarding www.premium-sponsor.com

Regarding the previous remark i'm just adding few points to finish: 1-I know that regarding the next version of www.premium-sponsor.com using php6 there will be several points taken in consideration(must be): 1- One function must receive one parameter that it's one array ...each time one function needs one extra parameter it's just added at the array... 2-The Point of the 'Databases independent from the rest' it's the logic of... Every sql compiled(procedures) or not(especific functions using api of abstraction for example) receiving parameters will generate files with sql results generated in serialized files,xml files,etc ... @cache... Each time someone executes points directly to the serialized file or xml(... no need to link directly to the database...)... Every sql by default(example update) ... updates permanently the record even if it's not necessary ... pushing it to the limit because if there is one day where one problem exists it's easy to desactivate the writting processes with one single flag... 3-Optimization of cache ... everything must be controlled with perfection... even the serialized,xml,etc files to be deleted(recreated for cache) ... well organized per section,sub sections,etc... (if the databases need one new structure,etc ..the rest won't be affected...) This flexibility of (re)organization that is required/essential nowadays ... especially looking at huge projects ... 4- Sessions ... the session of entrance (refererer-1,ip,etc) and at the end associated to one session of out(necessaries variables for the especific needs) ... Kind regards, Carlos Previous remark: ------------------------------------- Like i write i'm preparing in php4 and the next version of www.premium-sponsor.com will be php6 ... This project will always followi the next logic... 1-Database(s) ... independent from everything... This means that the website for example will be always pointing to serialized files to display the information and generate pages@cache,pages for tracking,etc ... Why? Because if there are needs to change the database structure(needs of reorganization,scability,etc) it won't affect the rest ... it's kind of obvious i'd say ... serialized files are generated ... and are only generated when it's necessary,logic,obvious,etc... Xml,etc files will be generated and placed at cache too, following the same logic of the serialized files... Sessions will be logged in text files,databases and memcache if needed ... I'll need in the nearly futur one experianced sysadmin dedicated to this project ... one experianced dbadmin .. and experianced programmers... I'll have to explain after the processes, how it works,etc,etc ... and for me it's relatively easy to explain ... and somehow not easy to understand because it's complex i'd write... And this project will be huge... organized per main sections,etc ... Kind regards, Carlos