Jeff Thorne wrote: > I have been reading that it May be more > efficient to just pass the resultset back to the view rather > Than deal with the overhead of several transfer objects. Does > this make sense?
I don't thinks so. 1. Object creation time is trivial compared with database access time. 2. Keeping the resultset open hogs database connection resources. 3. The gui and database should be independent, and free to evolve in different ways. There's hardly any point in using an MVC framework if all you're going to do is make it a direct face of database tables. You might want to consider using a single DTO at a time, based on the needs of the GUI screen/process. When running the GUI and Business tiers in the same VM, I would skip the DTO altogether and use an Interface, instead, for the Business API as seen by the GUI. This can be implemented by full-fledged domain objects. - George --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
