Comments on: Caveat when calling components from onSessionEnd() http://www.chapter31.com/2007/09/28/caveat-when-calling-components-from-onsessionend/ development in a land far far away... Thu, 28 Aug 2008 16:38:35 +0000 http://wordpress.org/?v=abc By: Michael Sharman http://www.chapter31.com/2007/09/28/caveat-when-calling-components-from-onsessionend/#comment-22078 Michael Sharman Sat, 29 Sep 2007 02:22:32 +0000 http://www.chapter31.com/2007/09/28/caveat-when-calling-components-from-onsessionend/#comment-22078 @Todd - Not harsh at all Todd, I appreciate the feedback. In hindsight that would have been the better approach, definitely! I must admit that sometimes when pressed for time (HUGE deadline on this one) and looking at someone elses code I can get caught up looking at the actual problem and not stepping back and looking at the bigger picture. That is something else to work on :) @Todd - Not harsh at all Todd, I appreciate the feedback. In hindsight that would have been the better approach, definitely!

I must admit that sometimes when pressed for time (HUGE deadline on this one) and looking at someone elses code I can get caught up looking at the actual problem and not stepping back and looking at the bigger picture.

That is something else to work on :)

]]> By: todd sharp http://www.chapter31.com/2007/09/28/caveat-when-calling-components-from-onsessionend/#comment-22019 todd sharp Fri, 28 Sep 2007 12:44:55 +0000 http://www.chapter31.com/2007/09/28/caveat-when-calling-components-from-onsessionend/#comment-22019 "Obviously arguments should be passed to components instead of being accessed directly, but that’s another story" That is another story, and I don't mean to sound harsh, but you might have wanted to fix the whole component while you were at it. A simple init() function which sets the dsn in the variables scope when the component is instantiated would have done the trick and ensured any other calls would not have the same issue. “Obviously arguments should be passed to components instead of being accessed directly, but that’s another story”

That is another story, and I don’t mean to sound harsh, but you might have wanted to fix the whole component while you were at it. A simple init() function which sets the dsn in the variables scope when the component is instantiated would have done the trick and ensured any other calls would not have the same issue.

]]>