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 your objects that needs to maintain the user info, then do:
myObject.setUserID(session.userbean.getUserID()) before commiting. Then have timestamp field in the db. ----- Original Message ----- From: "Mike Kear" <[EMAIL PROTECTED]> To: "CF-Talk" <[email protected]> Sent: Monday, January 08, 2007 7:51 AM Subject: A question about CFCFactory objects as a singleton .... > 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 have several hundred > concurrent users accessing the application. (in the past i've used it > for > things like a CMS where only one person is going to be using it for an > hour > or so every few days at most, so bottlenecks and performance issues are > still important but not as high a priority). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:265963 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
