Baz, In general, I use my tags only to do display stuff. I think that's the way to go IMO.
....................... Ben Nadel Web Developer Nylon Technology 350 7th Ave. Suite 1005 New York, NY 10001 212.691.1134 x 14 212.691.3477 fax www.nylontechnology.com Sanders: Lightspeed too slow? Helmet: Yes we'll have to go right to ludacris speed. -----Original Message----- From: Baz [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 18, 2006 2:55 PM To: CF-Talk Subject: RE: CFCs, TAGs, Locking The first suggestion! Thanks. It seems like it would work but coding locking stuff in EVERY tag just in case it *might* need it seems like a lot of overhead. Maybe the only solution is to never pass in objects and only pass in local structs to TAGs. That way you can be sure no weird modifications occur. Maybe its bad practice to have a TAG do anything besides display. Baz -----Original Message----- From: Ben Nadel [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 18, 2006 2:24 PM To: CF-Talk Subject: RE: CFCs, TAGs, Locking What about having an attirubte of the tag (LOCK) that defaults to false? When there are race conditions, are you going to know when they happen? Like, if the timing is contextual, you could put lock=true in the appropriate call to the tag? Never done that, but an idea.... ......................... Ben Nadel Web Developer Nylon Technology 350 7th Ave. Suite 1005 New York, NY 10001 212.691.1134 x 14 212.691.3477 fax www.nylontechnology.com Sanders: Lightspeed too slow? Helmet: Yes we'll have to go right to ludacris speed. -----Original Message----- From: Baz [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 18, 2006 1:10 PM To: CF-Talk Subject: RE: CFCs, TAGs, Locking Very good point Ben, I was waiting for such a comment. But what if the TAG *does* update itself? Perhaps it allows you to choose an ID and gets some info from the DB based on it? Plus there are no guarantees as to what's happening inside the CFC. Perhaps to return data it must update an internal variable first. You don't really know and you shouldn't have to, that's one of the beauties of CFCs. There must be a more secure, robust way of making TAGs scope agnostic. TAGs shouldn't have to know how the CFCs they are passed work or where they are stored. One bad solution would be to have a second trimmed down version of the CFC, that you use specifically to pass to TAGs. This CFC would contain only the methods that are safe no matter what scope the CFC is in. The problems with this are infinite though. Cheers, Baz ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:229939 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
