Is it *generally* good practice to use iterators to handle multiple values for an attribute - mainly for relationships between objects - rather than native types like arrays of objects or structs of objects (forget about the performance issues in cf)? The problem with using native types is that if you ever needed more logic, you would have to replace all handling of said arrays/structs with a new object anyway. So if you start out with an iterator that at first does little more than encapsulate an array, atleast you are future-proofing (I use that *very* lightly) the api. Agree?
Cheers, Baz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
