|
One reason might be that fact that the
iterator creates dependencies in application layers above the services if you
use it… having it in a Gateway is one way of isolating it so it is not
hardwired to the object. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Doug Hughes Why do that when there already exists an
Iterator object? <cfset ThingIterator =
reactorFactory.createIterator(“Thing”) /> Doug From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Shuck I was talking to a fellow developer about Reactor today and he asked if
a gateway had the ability to return not only a query, but possibly an array of
instantiated objects. My knee jerk reaction was that this is normally not
done and gateways normally return query recordsets, but I couldn't answer the
"why not?". Is it a bad idea for there to be some type of
getIterator() in the gateway that accepted a query recordset along the lines
of: |
- [Reactor For CF] is the idea of an iterator in a gateway f... Dave Shuck
- RE: [Reactor For CF] is the idea of an iterator in a ... Doug Hughes
- Re: [Reactor For CF] is the idea of an iterator i... Dave Shuck
- RE: [Reactor For CF] is the idea of an iterator i... Shannon Jackson
