In answering this question it is important to remember that Cold Fusion is a
separate step from any client side technology. That is the reason that one
can write dynamic javascripts. The Cold Fusion goes first then produces a
fully formed document to be returned to the client. From the client's point
of view it does not know that anything acted on the other side, all it knows
is that it was returned a standard HTTP/1.X stream. As long as you have set
the info coming out of the template up correctly then it should not
interfere with anything that happens "after" that point.
-----Original Message-----
From: James Husum [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 18, 2000 11:30 AM
To: Fusebox
Subject: Fusebox/XHTML
Greetings,
I've just started working with Fusebox and find it to be a good methodolgy.
I was wondering if anyone has started working with XHTML (something else
that I've just started looking into) and if they've run into any problems
with the Fusebox structure.
I can't forsee any problems with the two yet, but it looks like XHTML is a
bit stricter with its 'well-formedness' than regular HTML. Since Fusebox
does many CFINCLUDES to put together a page I was wondering if this might
turn into a conflict with the XHTML format.
James Husum
BiznizWEB, Inc.
http://www.biznizweb.com/
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
