RE: Translation - fast and dynamic plugin function and modifier
| From: | MPN | Date: | Sun, 24 Mar 2002 14:47:52 +0000 |
| Subject: | RE: Translation - fast and dynamic plugin function and modifier | ||
| References: | 1 | Groups: | php.smarty.general |
| Request: | Send a blank email to php-smarty-general+get-3316@lists.php.net to get a copy of this message | ||
OK, how about CMS like Web Portal.
-----Original Message-----
From: Roberto Berto [mailto:roberto@berto.net]
Sent: Sunday, March 24, 2002 3:04 AM
To: mpn@3dgamelink.com
Subject: Re: [smarty] RE: Translation - fast and dynamic plugin function
and modifier
I dont think a *NUKE programm can be called CMS.
Atenciosamente,
----------------------------------------
Roberto Bertó
Under Development
http://www.under.com.br
Tel: 51 32270599
Cel: 51 91169628
----- Original Message -----
From: "MPN" <mpn@3dgamelink.com>
To: <smarty@lists.ispi.net>
Sent: Saturday, March 23, 2002 3:46 PM
Subject: [smarty] RE: Translation - fast and dynamic plugin function and
modifier
> Good point. It wouldn't scale well at all, in fact most servers would
> probably choke with that kind of load.
>
> The website I'm working on isn't being done from scratch. I'm on the dev
> team for MyPHPNuke (MPN) and we are in the process of a complete rebuild.
> Considering that it is entirely possible to have more than 100 or more
users
> at the same time, the database approach would not be the preferred
> alternative due to the server overhead it would generate.
>
> However, due to the world wide usage of MPN and the need for efficient,
> viable translation, a static and a dynamic solution would offer much
greater
> flexibility to the users of the CMS.
>
> Keep the ideas coming, your input is valuable!
>
> KT
>
>
> -----Original Message-----
> From: Aapo Laakkonen [mailto:aapo.laakkonen@giro.fi]
> Sent: Saturday, March 23, 2002 10:09 AM
> To: smarty@lists.ispi.net
> Subject: [smarty] RE: Translation - fast and dynamic plugin function and
> modifier
>
>
> > This looks like a viable alternative.
>
> Only scalable tranlation approach I know is pretranslate the whole app
> before deploying. Binarycloud uses this kind of approach. So, you have
> to build your site with some kind of "make" process and get
> pretranslated version of your app.
>
> For smaller apps database or simply text file will do the job, but it
> still does a lot of overhead that is unnecessary. For example figure 100
> translations on one page? It hits 100 times database for one user. If
> there is 1000 users same time then there is 100000 hits to database. How
> do you think this would scale?
>
>
>
> ---
> You are currently subscribed to smarty as: mpn@3dgamelink.com
> To unsubscribe send a blank email to $subst('Email.Unsub')
> Visit Smarty's homepage at
> http://www.phpinsider.com/php/code/Smarty/
>
>
> ---
> You are currently subscribed to smarty as: roberto@berto.net
> To unsubscribe send a blank email to $subst('Email.Unsub')
> Visit Smarty's homepage at
> http://www.phpinsider.com/php/code/Smarty/
>
>