Andrew's Ramblings

Where personal space is never enough

Why ColdFusion will not survive while Adobe own it

Back in 2009 while looking into the possibility of what ColdFusion ORM could bring to the table, I started to look at projects I had on the go and looked at how I could convert some of these over to using the new Entities. One of these projects was a forum based application that was using nested lists, so I looked at how other languages that had ORM where achieving this.

The article that I found (Nested Set Implementation) to be the easiest explanation that would work, would not work in ColdFusion as it is. Not to be determined to not get this too work, I set out to see how far I could get and get it working. The result of this is the following Blog Post ColdFusion and ColdBox creating and using Nested Sets with ORM, but one of the things that it has a problem with is flushing of Entities.

Are Game Companies like King and Gameloft killing the industry?

This is a question that I have been asking myself for awhile now, to be honest I think they are to some degree. As a developer I value my work as much as the next developer, as well as anything that I may release to potential customers. But to have a larger company come along and just tune out rip off after rip off, of existing games is getting a bit out of control.

My first experience was with GameLoft itself, they released their popular version of Uno & Friends onto the Windows 8 Store, within minutes of me playing I no longer saw a need to play it any more. Due to a small glitch in the game, it was and still is today, to cheat and get all the power ups at no cost to you. I figured I would do the right thing and report the issue to them, since then the game has had one update and the issue has not been addressed.

For the last few months I have been trying to find some places in my site that can be optimised, as with my previous article on caching in ContentBox, there are other things we need to look at and you may even be surprised with some of the results.

First lets look at my site, the site is running using ContentBox and caching options, so if the content is cached it can be delivered in a second rather than 6-10 seconds. However the one problem I have is the dashboard inside ContentBox itself, which is now in the process of being rewritten for some clients to give it better performance.

But while I have been doing this, I sat back and ran some tests with the way ContentBox does its ORM and with the way ColdFusion used to do it with the query tag and using ColdFusion ExecuteQuery to see what difference are between these options. One of these actually shocked me, even though I had blogged about this before, those results showed not much of a difference. However since then I have seriously a lot more records than I did then.

The tests that I used are defined below.

Known ContentBox issue and posting to Google+

Since Luis released ContentBox V1.5 I think was the version that introduced this bug, the problem is that when retrieving content from a cache.ContentBox sends back an HTTP status code of 203. The problem is that Google doesn't like this at all, especially when posting links onto Google+, because as the description of that code indicates, Google+ considers the content as not the Author who is posting it.

This was raised with Luis and the team at ContentBox, but so far after 3 months it still hasn't been fixed.

So how do we fix it then.

I have been meaning to blog about this for some time now, just haven't had the time to sit down long enough to write it up. Before I begin, if you haven't checked it out, then I suggest giving it a go.

Out of the box, going to have to pardon the pun there or maybe Luis intended it, anyway ContentBox out of the box is configured with basic settings to get you up and running, but there are some tweaks that one should begin looking into when moving current customers and future customers over to ContentBox.

One of these is the speed of ContentBox and using the underlying ORM framework in the manner that is used by ContentBox, for sites that are low in traffic, it is imperative that you look into some of the caching options to help out here. ContentBox is designed to be at the enterprise level to begin with, but has basic caching enabled for the average user, but scaleable enough to handle the most demanding of server loads. Which comes as a trade off to those like myself, where the traffic is too low to have the website running efficiently.

Upgrading ContentBox things you should know

After being contacted by Jonathan Perret the other day, with some guidance on how to upgrade his ContentBox installation. It was obvious that maybe others might not be aware of the steps needed, or where to even find the update files themselves.

As always the entire source can be found on Ortus-Solutions / ContentBox, however what most people don't know is that every patch and update can be found in the source as well, where all the updates can be found in the folder called workbench and patches with that. This is a list of every update that can be applied to ContentBox, as well as any manual patches that may need to be applied as well.

The steps needed will depend, from what version you are going to be updating from.

ColdFusion could do with better and improved Closure support

I can recall in the days of the ColdFusion 9 beta days, when people had been discussing how to implement script support for custom tags. I can say that a lot of people didn't look at the bigger picture, at least not back then anyway. I am glad that Adobe never implemented some of those suggestions, sometimes it might sound like a good idea in the smaller scheme but not when you think about the bigger scheme of things.

This got me thinking some more after Luis Majano posted on the Railo list and also raise an E/R #3648785 that I think, should not only be adopted for the reason Luis has suggested, but also adopted by the language in areas outside of what is being suggested.

Interesting Closure issues within ColdFusion 10

The other day I got notification that a bug I raised with closures, was to marked closed with a reason of no worth the effort. I raised this because there is a major concern, in regards to how it is suppose to work and how it actually works. I pinged Adam Cameron about what he thought, which he wrote a blog about this over at ;Not worth effort again from adobe.

However I feel that I need to go into some more detail as to why I believe this to be a problem.

Interesting ColdFusion scripting problems when refactoring code

Today I managed to solve an issue that has been plaguing me for months on end, which I began cursing Adobe again. Anyway, the interesting thing is the way it actually fails and if I do say so myself it really actually makes it hard to explain.

Interesting Coldfusion problem with dates

In the last few days, I had just got around to scripting the needed changes to update this blog, so that it was running the latest version of ContentBox. While just running through some quick checks to make sure everything still worked, without any dramas, I noticed one small difference between the content being displayed.

I noticed that one server was displaying the dates as mm/dd/yy and the other was displaying them as mm/dd/yyyy in the dashboard for recent posts etc., which had me stumped for awhile. Both servers where running the same version of ColdFusion, as well as the same Windows OS, so I dug deeper to find out what was going on here and the results are surprising.

« previous 1 2 3 4 5 6 7 ... 42 43 next »