|
|
|
|
"osCommerce core classes
------------------------
The intention of this so-called contribution is to provide a set of core classes that will bridge the gap between the core components of MS2 and the upcoming MS3 release.
With the initial upload three core components of osCommerce are provided.
osC_Database
osC_Cache
osC_Session
osC_MessageStack
osC_Cookie
osC_MessageStack class is required by the osC_Database class.
osC_Cookie now exists!
The old MS2-2.2 functions have been revised to use the above classes instead, in doing so MS2-2.2 stores can utilize MS2-2.2 specific code and any snippets of MS3 code that they can use or have the ability to start writing any new code in an MS3 type fashion. eg caching queries now becomes so much easier:
(see cache-configuration-readme.txt)
-------------------------
$Qcfg = $osC_Database->query('select configuration_key as cfgKey, configuration_value as cfgValue from :table_configuration');
$Qcfg->bindRaw(':table_configuration', TABLE_CONFIGURATION);
$Qcfg->setCache('configuration');
$Qcfg->execute();
while($Qcfg->next()) {
@define($Qcfg->value('cfgKey'), $Qcfg->value('cfgValue'));
}
$Qcfg->freeResult();
-------------------------
From a developers point of view it might be a good thing to do... and gives scope for improvements
i.e. it isn't perfect (yet?)...
Its long been my opinion that osCommerce should be developed and maintained as contributions.
This could be considered the same as when osCommerce start releasing patches.
By stripping osCommerce into contribution components the osCommerce community can then maintain the code, this may also generate further scope for people that would rather piece together an osCommerce application themselves, and variations of the components could be used, rather than strip and insert, it would then just simply be insert (which is generally easier to do), obviously there needs to be some core components" |
|
|
|
 |
| For more information, visit the official osCommerce contribution webpage. |
|
|
|
