is there anything wrong with a cfc returning a collection of objects? and
then treating each collection item as an object in it's own right?
You might run into performance issues, depending on how you're doing things. If you read a bunch of data from a database as a query and then convert every row to an object and place them all in a collection, that's potentially a big performance overhead. If the tree-structured in-memory model is very important, then it might be an overhead worth paying for.
I mean the object model for MSWord is
((((((char)word)sentence)paragraph)page)document)...etc
I doubt that Word really creates an object for every character (or even every word), even tho' the logical model behaves like that. Often the logical and physical models in a program are radically different and are mapped to each other using dynamic trickery (I've written a couple of word processors in my time and the physical representation of documents can get quite hairy when you're aiming for performance!). Programs often work with an aggregate model and only construct the discrete models on-demand.
Regards, Sean
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
