Back in early May I talked about presenting FW/1 at D2WC, the upcoming Designer/Developer Workflow Conference in Kansas City, MO. I was really looking forward to visiting a new city and trying out a new approach to presenting. Unfortunately, personal issues have conspired to rob me of that opportunity and I'm no longer able to make the trip. Fortunately, my esteemed colleague at Railo, Mark Drew, has agreed to take over my talk at very short notice so you can still look forward to:
- An introductory talk about FW/1 by a stout, bald bloke with a funny account - you'll hardly know the difference!
- Sponsorship by Railo Technologies, with a key staff member on site to answer all of you Railo questions and, hopefully, encourage you to let the Railo consulting team help solve your CFML problems!
What's new is the opportunity to take advantage of the comprehensive Railo Server Administration training course that Mark is running after the conference!
If you haven't registered for D2WC, there's still time. The conference offers an unparalleled blend of designer/developer topics focused on workflow and a host of expert speakers. I'm dead jealous of those of you attending!

3 responses so far ↓
1 Kerr // Jul 11, 2011 at 1:53 PM
2 Sean Corfield // Jul 11, 2011 at 8:04 PM
3 Kerr // Jul 12, 2011 at 5:44 AM
I wrote our current solution from scratch in 2006. I had myriad reasons for that, but I sometimes wish now that I hadn't made some architectural choices that I was backed into a corner on at the time. Our current solution isn't flexible enough for today's demand of data to XYZ devices. Still, I wasn't attracted to the XML config heavy frameworks of the day. If it takes me a lot of hours just to wireframe a site, the framework itself seems a bit imposing. I've had this experience ramping up with ColdSpring, though I really like the stuff I see in 2.0. That said, I have a feeling that the FW/1 philosophy applied to DI would be much to my liking. :)
It's funny you mention routes, as I was looking at those last night. I'm using subsystems and was attempting to set a route pointing to a non-default subsystem, and couldn't get it to trigger. I'm sure it's a matter of being new to them, so I will post to the group if I can't get it sorted.
One thing I was curious about was that routes must be set per-request? Looking at the architecture, I suppose an app level cache to set variables.framework.routes in setupRequest() is not out of the question though.
Time and priorities being what they are, I have been keeping a passive eye on cfmljure too. While I don't know Clojure, that it could be leveraged in the way you explain with the model layer is very intriguing.
Thanks for sharing all that you do, it's much appreciated.
Leave a Comment