Well, as promised, more documentation is now available to support the upcoming 2.0.0 release. Here is a breakdown of the updated guides:
- Coldbox Overview Guide
- Coldbox Features & Capabilities
- Coldbox System Requirements
- Coldbox FAQ
- Coldbox Compatibility Guide for 2.0.0
- Coldbox Install Guide
- Coldbox Settings Guide
- Coldbox Config.xml Guide
- Coldbox URL Actions Guide
Here is a listing of new guides:
- Coldbox Caching Guide (In progress)
- Caching Objects Example (completed)
Click here to go to the trac site and read these guides. More will be updated soon, so please be patient and keep enjoying the 2.0.0 beta.
Add Your Comment
(2)
Mar 04, 2007 09:12:20 UTC
by Sam Farmer
Luis, This is all very impressive. Is it possible to directly call a controller cfc? I may need to do this for some remote calls (webservices, etc) and would want to the call to be something like: address.cfc?method=get&id=4
Mar 05, 2007 12:29:28 UTC
by Luis Majano
Hi Sam, This is possible. You can create a remote event on it that can return data to you. But you are bypassing the framework execution. So, most likely any framework related calls would fail. So there are two options 1) You make the remote method call but without any use of the framework (sort of defeats the purpose). Why? well, remember that coldbox injects the handler object with the running controller and with the request context. You can still use this technique but without using the framework calls. 2) Use the framework. How? Well, you would call index.cfm?event=ehTools.getSomething&id=4 Then in your event you will have to do your logic and you can use the framework architecture. As for returning the data, you can set the data to return on the request context: context.setValue("data",mydata) and then create a view that basically dumps the data to return back to the remote service. This is how I have integrated to Ajax. However, I this is a good view of how to activate a method for remote execution. I am taking my notes on this. Thanks, very good point.