Into external module, use dol_include_once.
Because this are 2 different situation, i don't think it is a problem to have 2 different code line.
Also discussion started to say, we can move "core code" at a different place. I think we should ask differently: Why allowing to change official structure of trees into a different one ? This may lead to difficult way to understand.
But may be you are speaking of directory "scripts" only ?
2014-08-14 9:13 GMT+02:00 Doursenaud, Raphaël <address@hidden>:
@marcos You're talking about an autoloader, right ?Laurent voiced against it at latest devcamp.2014-08-13 11:22 GMT+02:00 Marcos García <address@hidden>:
What about looking for a better solution that avoids us from constantly including dependencies and allow Dolibarr to handle them?Regards,2014-08-13 11:19 GMT+02:00 Florian HENRY <address@hidden>:Laurent made a study about performance lost when using only this method and he tell us dirung the devcamp there is a real difference. After that, If you have 3000 dolibarr install on only one server, you can see the difference but with one dolibarr per server it will not impact so much.
I will be agree with Christophe and Maxime, I prefer a full customizable dolibarr rather than cloud performance oriented.
Florian Henry +33 6 03 76 48 07 address@hidden http://www.open-concept.pro Twitter : @_Open_Concept_ Google+ : https://www.google.com/+Open-conceptProLe 13/08/2014 11:06, Marcos García a écrit :
It is. Performance decreases because every time you include a file, it has to check if it has been included yet or not.
Regards,
2014-08-13 10:25 GMT+02:00 Maxime Kohlhaas <address@hidden>:
Hi.
I agree, I got used to put "dol_include_once" function whenever I need an inclusion. Even for core modules.Is there any disadvantage doing this ?
2014-08-12 18:14 GMT+02:00 Christophe Battarel <address@hidden>:
Hello everybody,
I wonder if there are reasons to keep require_once lines in dolibarr except for performance issues.
Because if we replace every require_once by dol_include_once, it will be possible to customize any script of dolibarr by putting them in the custom directory with the right pathes.
Best regards
Christophe
--
Christophe Battarel
Responsable technique
sarl altairis
Informatique et Web en Grésivaudan
33 Grande Rue
38570 Goncelin
09 52 71 70 96 (appel local)
address@hidden
http://www.altairis.fr
_______________________________________________
Dolibarr-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
_______________________________________________
Dolibarr-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
_______________________________________________ Dolibarr-dev mailing list address@hidden https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
_______________________________________________
Dolibarr-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
_______________________________________________
Dolibarr-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
--Raphaël DoursenaudDirecteur technique (CTO)
Technopole Hélioparc2 avenue du Président Pierre Angot64053 PAU CEDEX 9SARL GPC.solutions au capital de 7 500 € - R.C.S. PAU 528 995 921
_______________________________________________
Dolibarr-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
Laurent Destailleur (alias Eldy)
------------------------------------------------------------------------------------
Social networks of my OpenSource projects:
Dolibarr Google+: https://plus.google.com/+DolibarrOrg/
Dolibarr Facebook: https://www.facebook.com/dolibarr
Dolibarr Twitter: http://www.twitter.com/dolibarr
AWStats Google+: https://plus.google.com/+AWStatsOrgPoject/
AWStats Facebook: https://www.facebook.com/awstats.org
AWStats Twitter: http://www.twitter.com/awstats_project