Blog

I just realized that I got nominated to speak at the Frameworks Conference in DC in February. So if you really support ColdBox and would like a ColdBox 101 session for this conference, then go to the link below and vote for me. http://www.frameworksconference.com/survey.cfm Thanks again for your ColdBox support.

I just created the ColdBox Google Groups Mailing List. You can use it for solving issues, bugs, discussions or anything you like. Also, if you forward any messages to bugs@coldboxframework.com and it is a valid bug it will be started as a discussion also if need be. Here is the info:

• Group name: ColdBox: A ColdFusion Framework
• Group home page http://groups-beta.google.com/group/coldbox
• Group em...

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 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

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)

This is a question for you to answer. ColdBox supports the mode of being in debug mode or not. It does so, by placing a cookie on your browser so you can see the debugging panel only with that cookie set. The question is, how long should that cookie live? What should the expiration time be? Any suggestions?

I think that a standard is arising on the way a method is injected with a request bus. My naming was requestContext and I believe mach-ii and fusebox use both event. I think it would be benefitial for developers for me to change this to event. What are your thoughts on this? This would help if a developer wants to switch from one framework to another or doing a transition, if some of the similar elements shared in an MVC framework can remain the same. I a...

Thanks to Mr. Charlie Griefer, we just set up the ColdBox IRC channel. You can connect to it via DALNET and then just join the coldbox channel. I will be mostly connected at night (Pacific Time). This channel is to promote more live responses from the ColdBox community. You will be able to ask me any questions about ColdBox and more of the veteran ColdBox users will also log in and share ...

I know this is late, but I have been swamped at work, so things have been slow.
Sean Corfield has blogged about ColdBox, over at http://corfield.org/blog/index.cfm/do/blog.entry/entry/ColdBox and does a mini-review on it. He also asks ColdBox users to give their opinions on why they chose Coldbox? Why they like it? etc? Some people...

As ColdBox has gathered steam and continues to do so, development for the 2.1.0 release has already begun. We are also in need of your observations and suggestions. We have gotten several wishlists and feature requests that will be implemented for version 2.1.0