Blog

I recently found some great comments about a user commenting on ColdBox, why it exists, why create it, etc. I found it enlightening because, not many people have used this yet, it is fairly new to the open source community and it is my job to write more about the nature of ColdBox and using a coldfusion framework. So to introduce the article I have to note that ColdBox is another tool for web application development. Just like mach-ii and model-glue. Some people want competition and which one is the best. I do not believe in that. I believe in cooperation and finding the best solution to a problem, no matter what. I even wish that all the framework authors can join and create a solution. (Anybody listening?? A standard??) So please understand, that object oriented approaches and enterprise level application architectures will be complex and you should study upon them. Here is my article:

I have been deliberating whether to open the SVN repo to anonymous access so people interested in the project can actually test new builds and ideas. Since the framework has been receiving an overwhelming response and my commitment to the project has been growing and brewing. I have decided to open SVN access to the repository. Below you will find the connection information.

CAUTION: checking out the latest builds, means using bleeding edge and probably not yet tested software, ...

I have had some suggestions for the fwreinit flag to be protected in order to reinitialize the application at hand. What do you think? Is this overkill? The application reinitializes, but it does not crash. It just adds some extra cycles to the request in order to clear and reinit the app. Please send me your comments, suggestions? Should an application reinit, be password protected? Thanks, Luis

After spending a very productive ColdBox weeked, here are some links that you will find interesting:

Milestone for 1.2.0 Matures

Milestone 1.2.0

FAQ Updated

FAQ

Announcing ColdBox Cache!!

This will make some users happy!! I am still on the planning and research phase, but putting a...

I just opened the announcement of ColdBoxReader. A coldfusion based RSS reader that comes included with the ColdBox Bundle. I will be separating this project and enhancing it according to community needs. So please give your opinions and suggestions on this project. As of now, it is part of the ColdBox project and will continue in its same timeline. The link is http://coldboxreader.riaforge.org/ So please enjoy and bring me your comments and ...

Just a quick note, that I was impressed today to see that more than 500 downloads have been registered for ColdBox since I opened the project back in August. I am really grateful that this framework is having great response even in its infancy. Thanks again for your support and please continue to support Open Source Projects. Have a great X-Mas and a happy New Year. May God bless your coding brain cells and soon to be carpetunnel fingers.

You can head over at CFDJ for a great frameworks article by Faisal Abid : Frameworks, Frameworks, Frameworks http://cfdj.sys-con.com/read/317576.htm It talks about why frameworks should be used, their role and how they can help application development. The article mentions ColdBox and some of its features.

For those of you interested in testing the upcoming 1.2.0 ColdBox release, please download it from the repository and give me your feedback. I have just finished uploading a stable version. Some of the new and interesting features are the following:

ColdBox Event Handler Caching

If you thought that ColdBox was a fast framework, well it just got faster. With the flick of a new setting HandlerCaching your application will cache the event handlers. This o...

This is more of an announcement of the upcoming 1.2.0 features. Since event handler caching will be instilled into the framework, the performance is dramatic. It actually, does not make sense to be creating event handlers for each request. So version 1.2.0 will be the last version to support uncached handlers. The versions after 1.2.0 will have caching of handlers by default. I see no benefit of not caching the handlers. And they can easily be recreated by using fwreinit= url command So. Since event handler caching actually changes A LOT in event execution. The methods will receive the request collection object, instead of the handler being injected with it at creation. What does this imply? Well, mainly the 'rc' scope will become deprecated. You can keep it, however, you must var scope it locally. Example: var rc = arguments.oRC (or whatever the argument is named, still pending)

My good friend and collaborator Aaron Conran, just posted a very interesting article on how to migrate your fusebox apps to coldbox. Also it explains some of the benefits you achieve. You can find the article here Transitioning from Fusebox to ColdBox