Last night Ben Nadel sent me an email asking if there was any way to get the currently executing function so you could get the metadata from it.
<cffunction name=”test” myAttribute=”1″>
<— How can we get the myAttribute value? —>
</cffunction>
The first obvious attempt at this is to use getMetaData(test).myAttribute, and that works fine until you [...]
14
cfimage and ImageScaleToFit on Large Images Pegs CPU
5 Comments | Posted by Elliott in Adobe, ColdFusion, Programming
I was working on the new profile picture feature of the registration and CFUnited 2009 website when I ran into an issue where a user uploaded a 2112 x 2816 (2MB) photo.
This seemed to cause file locking issues in cfimage which I was told were addressed by CF 8.0.1 Cumulative Hot Fix 1. I [...]
1
ColdFusion 8 Exception Handling Breaks HTTP Requests
0 Comments | Posted by Elliott in Adobe, ColdFusion, Programming
Just found this bug today….
So CF8 outputs the cfcatch.message into the Reason-Phrase portion of the HTTP Response, however it does not strip new lines (LF or CR). A web server, however, should never send new lines in the Reason-Phrase [1], and should probably be truncating that error message at a certain length.
[1] [...]
17
Getting the Expected Results for GetCurrentTemplatePath() in a Custom Tag.
8 Comments | Posted by Elliott in Adobe, ColdFusion, Java, Programming
While working on the template system used for the conference websites I ran across a problem where I needed the path to the template that called a custom tag. The first thing I tried was getCurrentTemplatePath() thinking that it might return that since the documentation makes no mention of custom tags. Instead, however, the function [...]
25
ActionSctipt 3.0 Array Access Woes
0 Comments | Posted by Elliott in ActionScript 3.0, Adobe, Flex, OS X
With the recent launch of Apollo Beta I thought I’d look into Flex again for some fun and decided I’d write plist api so that Apollo applications could read and modify OS X plists in a sane maner.
PList XML is particularly problematic because of how its structured:
<dict>
[...]
While doing some casual web surfing I came across a rather interesting blog entry about Ruby’s types and looping. I started typing a reply, and then I realized it was really long, so I’m putting it here:
One reason I think methods like this are great is that Ruby is intended to be read! Which actually [...]