Re: [Reactor For CF] Reactor R&D

[Kurt Wiersma]

You can see example how we handle the one to many situations in the example app Shannon posted above. Basically we cannot argue to much with how Reactor uses the iterator object since there is not standard in CF for handling collections of CFC beyond arrays (which are hard to proxy for lazy loading).

I work with Shannon to write a more complete description how we are planning on handling this.

--Kurt

On 3/24/06, Sean Corfield < [EMAIL PROTECTED]> wrote:

Yes, I believe that is exactly the point Kurt and Shannon are making
and, yes, that's why it makes perfect sense to them (and, taking my
horns and tail off for a minute, I found the "Record" suffix annoying
when I first started using Reactor for exactly this reason).

As Doug says, I'd like to hear more about how they handle collections
/ iterators etc.

On 3/24/06, Jared Rypka-Hauer <[EMAIL PROTECTED]> wrote:
> I think what I'm realizing is that (consider a User Reactor object) you see
> getFirstname() (returns string), getLastname() (returns string), and
> getAddress() (returns Address) or getUserRole() (returns UserRole) as being
> the SAME KIND OF OPERATION. They're getters that return properties from the
> User bean... whereas getAddressIterator() returns a utility object that
> isn't a straight-up getter for a simple or complex property of the object...
> is this a correct summary of your perspective?
>
> From THAT PERSPECTIVE, I suddenly see why it makes sense to you... you don't
> see methods like getFirstnameString() or getZipCodeNumber() so why see
> methods like getAddressRecord()... right?
>
> Am I on the right track here?



-- Reactor for ColdFusion Mailing List -- reactor@doughughes.net
-- Archives at http://www.mail-archive.com/reactor%40doughughes.net/

-- Reactor for ColdFusion Mailing List -- reactor@doughughes.net -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/