Welcome to the 6th entry in my newbie ColdFusion contest. Today's entry is by Joe Zhou. His entry didn't have a name, but referred to the Monster so that's what I'm calling it. His entry has a few graphics in it that are copyrighted, so as with the last few entries I'm not putting a demo online. I do encourage you to download it (use the Download link below), and check it out.
This game was especially difficult for me. Maybe I'm just a bit slow (very possible), but I was unable to make this Monster happy no matter what I did. I was able to change various stats (his monster allows for feeding, playing, and resting), but his overall status went from bad to worse. As a side thought - it would have been truly evil if a user had submitted an entry that was impossible to win. Especially if it was really subtle. You would work, and work, and work, and slowly but surely your creature would die, but still leaving you thinking that next time - maybe next time - you could save it. Evil. But I digress. Now that you've checked out the demo, let's talk about the code.
As with a few other entries - I'm going to complain about him not using index.cfm. His docs explain which file to hit first - but it really shouldn't be up to the docs. I'm wondering if he (and the other entries), were maybe a bit confused about how to correctly "push" a user if not logged in/registered. This could be done easily enough in Application.cfc/cfc. So for example, a simple "is logged in" check could be done like so:
<cfif not structKeyExists(session, "loggedin")> <cfinclude template="login.cfm"> <cfabort> </cfif>
Moving on - I thought this was a bit odd:
<cfapplication sessiontimeout= "#CreateTimeSpan(0, 5, 1, 0)#" sessionmanagement="yes">
Specifically the 5 hour session timeout. The default is 20 minutes, and while I've seen 30, or 40, 5 hours seemed... excessive. Although if you look at the ColdFusion Administrator, the max is set to 2 whole days. Does anyone else use high timeouts like this?
Another problem. Consider main.cfm. His code cfparams url.action. Which is good. Never assume a URL/Form/Cookie variable actually exists. Users (especially people like me) can muck with values and remove/change them to see if they break your applications. As an example, if url.action is "", this code is run:
<cfset user = oUser.loginuser(username=#form.username#, password=#form.password#)>
With no cfparam for the form values, it is possible that an error could be thrown here.
Another issue: HIs application makes use of an XML file (with WDDX data - what in the heck - I thought no one used WDDX anymore!) to store the user data. While I liked this - it does bring up a security issue. I can easily view the XML file in my browser and see all the usernames and passwords in plain text. This can be fixed easily enough in much the same way I "protected" the XML data/ini data I use in some of my open source applications. I simply switched from an XML/ini file extension to a cfm extension. I then wrapped the data in CFML comments. This means if someone requests the file directly, they see nothing.
Lastly, let me talk about his CFC, userinfo.cfc. His CFC handles the processing of the WDDX file I mentioned in the last paragraph. I liked this CFC, although he made the output/var scope issues that most others did. Then again - I tend to be pretty anal retentive about my CFCs!