Thursday, January 26, 2006

Is cfproperty necessary for the Flex2 CFAdpater?

At the very top of the of the User.cfc in the UserManager sample application, I notice the there is a note that says:

In order for this CFC object to map correctly to an actionscript class, we must define each public property and the type, which maps to the public properties of the actionscript class.

It's followed by a cfproperty tag for each public property in the user object. It has been my experience that cfproperty does pretty much nothing unless you are trying to define a hash-map in a web service. Has this changed with respect to the CFAdapter? If I comment out the tags, the application appears to still work (although I seem to have some issues with caching sometimes).


I have posted this entry in Labs as well.

Thursday, January 19, 2006

CF hiring market heating up?

I'm generally not in favor of business combinations that diminish the number of participants in the competitive landscape. The acquisition of Macromedia by Adobe was no exception for me. I was pretty strongly against it from the beginning since I saw little benefit from the merger for the customer base of both companies. I'm sure that most businesses that had a desire to use the products of both companies already had relationships with each of them.

I also feel that most mergers of this type generally involve sacrificing some talented people in the quest to eliminate redundancies; a genuinely unpleasant situation for you if you happen to be one of those made redundant. Lack of competition generally leads to increases in pricing for products that loose competitors to the detriment of customers.

Over the last month, however, I've personally noticed a sharp increase in the demand for people with ColdFusion skills. Is it possible that Adobe really DID bring something to the table for Macromedia customers? Could it be that the simple recognition of Macromedia by an enterprise class vendor like Adobe as an acquisition target raises the profile of Macromedia technologies in the eyes of enterprise decision makers? I certainly hope so. If that is the case, I can only see that as a win/win/win for Adobe/Macromedia/combined talent base.

There are certainly lots of other factors that could contribute to the situation including time of year, pent up demand from the merger uncertainty, general economic outlook, maturity of technologies, etc. ad infinitum. My experience is purely anecdotal, so it could easily vanish like a wisp of smoke. Until it does, though, I guess all I can say is "cheers to 2006" and mark this as yet another instance where I was completely wrong (crap).

Given the choice between higher earning potential and being able to say I was right, I don't really have to think to hard about it. Feel free to call me stupid if you want to back it up with a check .

Anyone else noticing a change?

Thursday, January 12, 2006

How to make RequestTimeout work

Here's another beginner tip for an issue that had me hunting around for over an hour (Doh!). Since CFMX, the cfsetting tag has had an attribute called "requesttimeout". It allows you to force a long running page to use a longer timeout in seconds than is set in the administrator. I've used the cfsetting tag a few times since CFMX came out and I just figured it was one of those things that seems to not work as I expect sometimes. The requesttimeout attribute of the cfsetting tag is supposed to override any value set in the ColdFusion Administrator.

The keyword in that last sentence is override. It does not act to actually enable the request timeout feature of cf. If you don't have the checkbox and a default value set in the administrator, the value you set with the cfsetting tag doesn't have anything to override.

Your mileage may vary on this next point, but it is what caused my confusion for the longest time. If you don't have the checkbox in the administrator selected, you might expect all of your requests to run until they finish. What I have found is that in most cases, timeouts get taken over by the webserver settings. In my case, IIS has a cgi request timeout value that seems to kick in if I don't have request timeouts enabled in cf.