I'm more old fashioned, doing scripts by page edits, and I'm interested in how these Extension Installs work. So I can make them, and fix any that may need a tweak here and there when something becomes outdated.
1. Do they add or modify script on pages, or are they more of a program that just works?
2. How can the script for Extensions be accessed for tweaking if tweaking is needed?
3. What are the bad impacts caused by using Extensions vs editing script pages manually?
I'm just trying to make it short and simple , explained, as I'm able to, not beeing of english origin:
If a Page is called by a visitor, the Server collects all data, required to 'construct' the Page. To do this, in a Framework- Shop- Environment, requires many Tasks, Comparances, any many 'Results' are stored temporarely, to be used, to create the final Page Output Temp File.
Then, if everything has been done, a FINAL Temporary Files will exist, ready to be served to the Web. THEN, XML Files come into the Game, one after the other, starting from a to z. Every Single XML File Content will be be compared, individually, with the LATEST existing FINAL Temporary File Content, if an XML Files contains a DIFFERENT Content, or an ADDITIONAL Content, or even a 'Command' to REMOVE existent Content, it will be done, and another LATEST FINAL TEMP File is been created.
Every XML File will be handled this way. One after the other. Until the last FINAL Temporary Outpot File exists. Then, this File will, finally, be sent to the Visitor.
---
A lot of work, actually. 14 Years ago, it would not have worked out, at least not on shared Servers. Still, it works today, at least, most of the time, despite of the fact, that probably Masses of OC v.1.5.x Shops exist, containing 50, 60, 80 or even more different VqMods.
But strictly technically, it's just a Quick-Fix, a bad one too - if used in Masses, at best, to test something, but that's about it. As beeing one from Yesterday, we where teached the opposite way, or then, our Scripts would never even have worked, on a 4 MB of Ram, and Servers with 300 MHz CPU's....
---
But I use 'em too! Despite of what I wrote above. Mostly, because I am to lazy to implement their Content into the Source, and Second, because I want to avoid to run into Problems, when trying to add a new Mod, not working, because I modified the Source already, and the Mod does not longer FIND it's ANCHOR in the Source to make it work.
So, there are lot's of GOOD reasons, to work with XML-MOD's, and leave the Source, as it is. At least, if the Software, as it comes, is still under Construction, as it seems with OC Version 2.
---
But if you want to make it right, the OLD WAY, then, go to work and implement the Content 'CODE' of the XML Files into the Source. Or then, at least, 'combine' multiple Mod's doing their work in the same SECTION or Page, into one MOD, to avoid multiple tasks, wherever possible. It will keep your Server from doing a lot of work, internally, from building hundred Temporary Final Pages, before even serving Content, per Visitor CALL! And it would enable A LOT OF of Peoples, at the SAME Time, to visit and use your Shop, without taking the Risk of beeing confronted with sudden Server Timeouts and other ugly Messages, leaving the impression of an underpowered, so rather unprofessionally operated Place to shop.
But if a Shop only gets 100 Visitors/Customers per day, they probably won't feel a difference anyway.
So, it may just not pay out, to make OC to work as it really could, if it would, if done by a real Professional Setup.
---
The mayority of OC-Users would probably run into a lot of problems, trying to implement Mod's into Source. From that point of view, XML-Mod's are a great Alternative, easy to implement, and easy to remove as well.
Take it as it comes, it's not meant to be critical, you asked for something like it, I assume...
You all have a great 2015!
Ernie
openshop.li
If a Page is called by a visitor, the Server collects all data, required to 'construct' the Page. To do this, in a Framework- Shop- Environment, requires many Tasks, Comparances, any many 'Results' are stored temporarely, to be used, to create the final Page Output Temp File.
Then, if everything has been done, a FINAL Temporary Files will exist, ready to be served to the Web. THEN, XML Files come into the Game, one after the other, starting from a to z. Every Single XML File Content will be be compared, individually, with the LATEST existing FINAL Temporary File Content, if an XML Files contains a DIFFERENT Content, or an ADDITIONAL Content, or even a 'Command' to REMOVE existent Content, it will be done, and another LATEST FINAL TEMP File is been created.
Every XML File will be handled this way. One after the other. Until the last FINAL Temporary Outpot File exists. Then, this File will, finally, be sent to the Visitor.
---
A lot of work, actually. 14 Years ago, it would not have worked out, at least not on shared Servers. Still, it works today, at least, most of the time, despite of the fact, that probably Masses of OC v.1.5.x Shops exist, containing 50, 60, 80 or even more different VqMods.
But strictly technically, it's just a Quick-Fix, a bad one too - if used in Masses, at best, to test something, but that's about it. As beeing one from Yesterday, we where teached the opposite way, or then, our Scripts would never even have worked, on a 4 MB of Ram, and Servers with 300 MHz CPU's....
---
But I use 'em too! Despite of what I wrote above. Mostly, because I am to lazy to implement their Content into the Source, and Second, because I want to avoid to run into Problems, when trying to add a new Mod, not working, because I modified the Source already, and the Mod does not longer FIND it's ANCHOR in the Source to make it work.
So, there are lot's of GOOD reasons, to work with XML-MOD's, and leave the Source, as it is. At least, if the Software, as it comes, is still under Construction, as it seems with OC Version 2.
---
But if you want to make it right, the OLD WAY, then, go to work and implement the Content 'CODE' of the XML Files into the Source. Or then, at least, 'combine' multiple Mod's doing their work in the same SECTION or Page, into one MOD, to avoid multiple tasks, wherever possible. It will keep your Server from doing a lot of work, internally, from building hundred Temporary Final Pages, before even serving Content, per Visitor CALL! And it would enable A LOT OF of Peoples, at the SAME Time, to visit and use your Shop, without taking the Risk of beeing confronted with sudden Server Timeouts and other ugly Messages, leaving the impression of an underpowered, so rather unprofessionally operated Place to shop.
But if a Shop only gets 100 Visitors/Customers per day, they probably won't feel a difference anyway.
So, it may just not pay out, to make OC to work as it really could, if it would, if done by a real Professional Setup.
---
The mayority of OC-Users would probably run into a lot of problems, trying to implement Mod's into Source. From that point of view, XML-Mod's are a great Alternative, easy to implement, and easy to remove as well.
Take it as it comes, it's not meant to be critical, you asked for something like it, I assume...
You all have a great 2015!
Ernie
openshop.li
My Github OC Site: https://github.com/IP-CAM
5'600 + FREE OC Extensions, on the World's largest private Github OC Repository Archive Site.
Who is online
Users browsing this forum: No registered users and 7 guests
