On Thu, December 9, 2004 4:52 pm, Ronald West said: > Thanks for the replies, would either of you agree that this may be an > issue > with the type of task you are planning on executing, or that it does not > matter?
You're right, it definitely needs to be taken in the context of the kind of task you're executing. As illustrated earlier in that fine test, there may have been some misconceptions with respect to "rabid memory consumption" by CFEXECUTE. On the other hand, if you're going to use CFEXECUTE to invoke any long running (or potentially long running) process you may want to rethink that approach. There's nothing worse that having something a task get interrupted because the user decides to stop or refresh the page because it's taking too long to load. With an RDBMS you can use a transaction to make sure that an interrupted request doesn't leave your data in an improper state; I don't know what you could do to ensure that a CFEXECUTE call could be nearly as robust. -Cliff Meyers ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Gold Sponsor - CFHosting.net http://www.cfhosting.net Message: http://www.houseoffusion.com/lists.cfm/link=i:14:3783 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/14 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:14 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.14 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
