SV: [phpGroupWare-developers] Tuning: compability and speed

[Sigurd Nes]

> From: Dave Hall address@hidden
> Sent: 2007-03-22 15:35:30 CET
> To: address@hidden
> Subject: Re: [phpGroupWare-developers] Tuning: compability and speed
> 
> On Thu, 2007-03-22 at 15:09 +0100, Sigurd Nes wrote:
> > Hi all,
> > 
> > 1)
> > The utf-encoding is a real pain for IE.
> > Half of the times IE won't recognise the charset given in the meta-tag
> > - causing the page to freeze when redirecting.
> > A sollution is to set "AddDefaultCharset utf-8" in httpd.conf (not
> > sure what to do with non-apache-serves).
> > 
> > I propose a configurable charset - either "iso-8859-1" or "utf-8" to
> > choose from when installing the system - given by a variable like:
> > $GLOBALS['phpgw_info']['server']['charset']
> > 
> 
> I do not support this at all.  UTF8 is the future.  We support languages
> which use charsets other than iso-8859-1/15.  By switching to utf8 we
> can mix languages on the same page without a problem.  Keeping the lang
> files in sync for both charsets is a lot of extra work and has the
> potential to cause real problems.
> 
> We should look at fixing the UTF8 issues, not avoiding them.  
> 
> > 2)
> > The db-abstraction (referred to as phplib) from .16 is faster (about
> > 34%) than adodb used in head.
> 
> What is the peformance trade off of the additional layer that you are
> proposing here?  Have the tests been run on a range of data sets on both
> mysql and pgsql?  Running the same test 3 times on pgsql with 1 data set
> is hardly comprehensive testing and comparison.
> 
> 34% is a big difference.  At the same time added flexibility of ADOdb,
> not to mention that it is maintained are pretty big positives in my
> book.
> 

1)
If you have some ideas for fixing the UTF8 issues - I'm more than interested.
No need for lang files for both charsets: do a utf8_encode during install if 
needed.
http://php.net/manual/en/function.utf8-encode.php

2)
34% - try it on a heavy db-job - and you will be convinced (only tested on 
postgres - Mysql seems dangerous to me - if one do not use innodb). I'm not 
proposing to switch to phpblib - only as an alternative - which is easily done.

Regards

Sigurd