> Well another thing I found out this weekend reading through
> my ASP 3.0 book is two things I think are a little slow in CF.
> First is that you can program functions in ASP ie
>
> sub Calculate()
> code here
> end sub
>
> I dont know what the CF response to this is, perhaps the
> custom template comes closest. I suspect there is a "function"
> function in CF but not well versed with it yet.
There isn't anything directly equivalent in CF to inline functions in ASP.
The closest analogy, as you've mentioned, are custom tags, which allow you
to do anything which you could otherwise do with inline user-defined
functions.
> The other thing I am seeing in ASP 3.0 is extensive use of
> XML conversion without having to go through regex or WDDX
> as we do now. I havent read the full chapter but it looks
> like you can pull info from a XML data island right in ASP.
> There's a lot of WDDX stuff out there for CF right now but
> I'd like to see XSL for CF become more easier and widespread.
Keep in mind that the way you use XML in ASP isn't really analogous to the
way you use WDDX in CF (or to the way you can use WDDX in ASP for that
matter). You can work with XML "recordsets" in ASP, but WDDX is a bit
different in focus. WDDX allows you to move, transfer, or store data as a
string, and exchange that data with non-CF applications. Using XML with XSL
in ASP allows you to format data for a specific client, but you can
certainly do that using CF as well. In fact, that's typically what you do
with CF now, as it is! You grab data from a database, and generate HTML
output. Typically, when you're using XSL, you're simply moving the logic for
formatting data for a specific client from one place (your application
script) to another; this is a worthy goal when you already have data in XML
format, but if you don't then you'll have to build XML output in any case.
If you want something analogous to WDDX in the ASP world, there's Simple
Object Access Protocol (SOAP), which addresses many of the same concerns as
WDDX does, as well as others that WDDX doesn't address.
Finally, when you use all this XML goodness in ASP on the server instead of
on the client, you're doing this by automating the XML parser, which can
probably be done through the CFOBJECT tag within CF. I haven't tried
anything ambitious with this yet, though.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
