PROTECTED]
Sent: Tuesday, 9 January 2007 5:24 AM
To: CF-Talk
Subject: Re: A question about CFCFactory objects as a singleton
yes as a matter of routine, my tables usually have fields for:
createdby (the userid of the person who created this record)
datecreated (timestamp)
updatedby (The
Are you putting the entire factory into session or the results of the
factory?
It seems like to me that you put your factory into a less transient scope
like your application scope and then your user's session invokes an
instances of the factory as related to the user.
As for credentials, how muc
yes as a matter of routine, my tables usually have fields for:
createdby (the userid of the person who created this record)
datecreated (timestamp)
updatedby (The userid of the last person to alter this record)
dateupdated (timestamp)
So the methods in the DAOs that manipulate the records nee
It seems like option [B] would use a lot less memory resources.
A little more detail about how your objects are set up would be helpful to
get a clearer picture. Do you have multiple tables which each store which
user/ when created? It seems like you could have a userID property in each
of yo
I choose [B]. Less objects = a good thing.
On 1/8/07, Mike Kear <[EMAIL PROTECTED]> wrote:
> I'm building an app where usage is going to be FAR higher than anything i've
> used OOP for before, so I am trying to be careful to build it with the
> potential bottlenecks in mind. In this job i might h
5 matches
Mail list logo
