[pLog-svn] A terrible truth about plugin

Jon Daley plogworld at jon.limedaley.com
Sun Feb 3 08:25:11 EST 2008

On Sun, 3 Feb 2008, Mark Wu wrote:
> 1. About the  array_merge(), I just check the result again.... I think it is
> slow becasue the include(), not array_merge. In my test case, I need to load
> extra 14 locale files... So, there is nothing we can do with it...  :(
 	Do you see my (I think?) comment in pluginlocale.class.php:
// TODO: this function is only called once, right?
 	If that isn't only being called once, we could speed it up there, 
probably by having an if(!$this->_messages) surrounding that code.

> Maybe ask user or develer merge thier plugin locale into the core and reduce
> the file I/O access in thier production server.
 	Are you saying we should take all of the strings in the plugins 
and put them in the core files?  That is a lot of strings, isn't it - ie. 
normally people don't have all of the strings in their files, and my guess 
is adding all those strings, particularly when they aren't used would slow 
down the core?  Or are you saying people can do that on their own servers 
if they want to?  I am not particularly thrilled about either of those 
solutions.  Someone had suggested using defines or other methods instead 
of a big huge array of strings.

> 2. Do you have any ideas about the menu structure? Maybe I can try to
> implement it...
> 3. About the admin page cache, any ideas?
 	It seems that these two things will have a bigger impact on 
performance and less of an impact on future upgradability, etc. than 
putting plugin locale files in the core.

More information about the pLog-svn mailing list