trade off to more maintainable code, under the assumption it does not
affect the end user's view of the system. Once you see a noticeable
impact in doing it a simpler way thats when the situation should be
reassessed.
Adam
On Fri, 30 Jul 2004 15:11:00 +0200, Micha Schopman
<[EMAIL PROTECTED]> wrote:
> So because something is more difficult to do, we just take the situation
> which causes the most overhead on the server and stores duplicate data.
> Session variables can get you faster into trouble then application
> variables because the CMFX garbage collector is only called once a time
> and not on each request. So it is very important to minimize this types
> of situations :-)
>
> Micha Schopman
> Software Engineer
> Modern Media, Databankweg 12 M, 3821 AL Amersfoort
> Tel 033-4535377, Fax 033-4535388
> KvK Amersfoort 39081679, Rabo 39.48.05.380
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
