Blog

There has been a lot of talk recently about design patterns aimed at circumventing the overhead ColdFusion imposes upon us when creating CFCs. I'm not sure who coined the term "Object Instantiation Penalty", but the first reference to it I can find in the CF community was over at the Dot Matrix blog. Everyone seems to agree that object creation in ColdFusion leaves something to be desired, but I haven't seen anyone really quantify the price yet. I decided some line charts were in order.

I can never find this stupid page when I need it, so I am linking to it here so I won't lose it again. Use this when you want to download a specific JDK from Sun's site and don't want to wade through their confusing-as-heck "featured downloads" mess. http://java.sun.com/products/archive/ Update-- the URL appears to have changed. I'll put it here in case they ever deprecate the old one. http://www.oracle.com/technetwork/java/archive-139210.html

If you missed it, Jeff Chastain put up a very interesting post over at Alagad's Blog. Also good was the "spirited" discussion that followed between Barney and Peter Bell. I don't know how I feel about all of it, but the entire thing is very fascinating.

I've been staring at my computer monitor trying start this paragraph for about 10 minutes now, so I'm just going to start typing. I've been thinking about system design. Organization versus performance. Design patterns versus efficiency. We adopt some code without thought to its performance because we're talking about milliseconds, and the readability, organization, and structure gains our apps enjoy are well worth it. I'm not sure that is always the case though, and we don't notice it until too late.

The past couple of days I've been messing around with a couple functions, cleaning them up a bit to blog about them. One of them is for color-coding SQL and the other for highlighting differences in two strings. Both are pretty small, but very repetitive in what they do. Depending on the size of the text you are processing, performance varied. Sometimes the code inside was repeated hundreds of thousands of times given a large enough test.

Research shows that driving while extremely tired renders the same results as driving drunk. Following that same line of though, is coding while sleep deprived the same as writing your code in a drunken stupor?

I have a solution that I have gotten working locally to rid my ColdFusion logs of the annoying "Cannot create cookie" errors. For those of you just joining us, Teeps blogged it, Jochem explained it, I took a stab and it and failed, and now I'm back for round two. I apologize for blogging this so much lately, but once I get a good puzzle in my craw, I just can't let up until I've solved it.

Teeps started off the fun last month with this blog post about countless errors in his logs about not being able to set cookies. I get the errors too, and they usually look like this: 07/11 15:58:19 error Cannot create cookie: domain = .notingdetails.com 07/11 16:19:01 error Cannot create cookie: domain = .notingdetails.com 07/11 16:39:12 error Cannot create cookie: domain = .notingdetails.com 07/11 16:45:05 error Cannot create cookie: domain = .notingdetails.com

As promised, I have written a Java Servlet Filter to remove cookies from a request. If you don't know what a Servlet Filter is, read this blog. Let me start by saying while my filter does function like I wanted it to, it did NOT solve this problem. I'll blog on that next. UPDATE: Here are my findings Given that, I can't really think of a real-world use for this code, but I am always in favor of coding for the sake of learning.

In the Java world, web requests are handled by servlets loaded within a servlet container. There is a servlet mapping which specifies a servlet class conforming to Sun's Servlet specification which has been part of the J2EE spec since version 2.2. When a request is sent to the servlet container, it is matched to the proper url pattern and passed to the appropriate servlet object via that objects service() method.