Re: [Phpwebsite-developers] Language suggestion

[Bob T. <bo...@el...>]

Good points, but there may be good answers too.

Yes, it could be a bit slower, but since the entire site is database 
driven, how much difference would this really make?    If the 
calendar shows on every page, that is a pretty big hit on the 
database too.  Also the news blurbs in the right hand column.  All 
the pages are read from the database too.   Why would the language 
queries be special?

Also, there is a way to increase efficiency by storing frequently 
used phrases as session variables.

We would add one column to the language table to name the 
corresponding session variable.  Then instead of 
"show_program_message" we have "get_program_message", and return the 
value to the calling script.


Then, the language call would be:

if (!isset($sv_user_welcome)) 
   { $sv_user_welcome = get_program_message (mod=core,  
phrase='sv_user_welcome' )
 }

The session variable $sv_user_welcome is set inside 
get_program_message, and returned to the calling script.

This way, every individual language query is done once only per 
session.


On 20 Feb 2002 at 9:07, dyn...@us... wrote:

> Bob,
> 
>          Previously, the developers at Appstate mentioned that the
>          reason 
> they did not automate it in the script for others to control is
> because most people do not change their languages often.   It is a one
> time deal on average.
> 
>          The advantage is as you are thinking, but the disadvantage is
>          that 
> you would have to process that statement every time a user logs into
> the website.   This would slow down phpwebsite where it could be
> eliminated.   Of course this is all theoretical and maybe
> insignificant.    But I believe that was the logic for appstate to
> just translate it before it was downloaded.
> 
> 

--
Bob Treumann,  651-603-1245
Elmwood Solutions Inc. (St. Paul, Minnesota)
bo...@el...
http://www.elmwood.com
ORACLE Business Alliance Program Member