> be slighly faster, and they'll be more familiar as well (since you use
> them all the time). XML, on the other hand, will let you build the
> navigation with XSL, which can be very advantageous in certiain
> situations. In addition, you can use the XML document like a struct,
> though there are extra levels of nastiness in there (like xmlChildren
> and xmlAttributes).
My approach in this situation would be to create a CFC that queries the
Database, then another CFC to wrap the Query results in XML. Would that be a
proper "MVC" approach? Couldn't you view the WrapInXML() CFC as a proper
"controller" method?
Just curious if I would be overthinking it, or approaching it in a nice,
clean, "best practices" way. He's got one component that basically is his
"model" component, and anything that would wrap his results for any kind of
formatted output would be a "controller" component...is that right?
So you could even do something like, WrapInXML(GetMenuItems())...couldn't
you?
> One of the neat things about using XSL for your transforms is that you
> can let your system's users write the XSL (rather than you the
> developer), without fear that they'll be able to hurt the application
> or the system it's running on (aside from infinite loops and such).
> That's impossible with structs, becuase in order to use structs, you
> have to write CF code. Not sure if that's relevant to your situation,
> but it's something to keep in mind.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
