I Love ColdFusion

Anyone see any benefit for a blog engine to serve its CORE HTML from a Proxy?

This way when you mess with your templates you are never messing with the BASE application HTML, which I would like. Especially if what was coming in was SUPER defined and ease to understand.

ColdSpring can "look" at the request and then after the "whole request" is finished run a method, I'm thinking its called renderHTML which will deliver a XHTML. Then inside your templates you might have something like:

indexTemplate:
<!-------------------------- >
Posts<br/>
<cfoutput>
#getAllPosts()#
</cfoutput>
<!-------------------------- >

Now getAllPosts would return the approate fully formed XHTML so all you need to worry about it the .css styling.

Also if you ever wanted to change the XHTML the files would be in a "DisplayFoundation" directory.

I just like the idea of getting "displayObject" that I can put anywhere on the page and NEVER have to worry about "Forming" the dataObjects that are coming in from Model-Glue.

Just a thought or it might be complicated? I don't know, but you all are messing around with the blogs and would have a better perspective.

PS: I finally "got" ColdSpring this weekend. THANK GOD FOR COLDSPRING!!