Hi Greg,
Thanks for the response.
> Are you really saving *that* much time by taking on all the bad things
> that happen because of this?
The 'bad' things have to be dealt with whether you take this option or not -
DTOs are just another solution to solving the problems I described. Once
the graphing object is in place, it's only a couple of lines of code to
'copy' the objects - replacing that with DTOs and their mapping will
definitely take longer (and require maintenance too). But it's a fair
point - typing is NOT the slowest part of coding, so I can't say for sure
that it saves me time (it's not quantifiable, it's personal preference, and
I did say 'hopefully' saving time).
> If it is a substantial portion of your time that would mean that you
> are heads down coding CRUD stuff by hand where typing speed becomes
> valuable? Could you code generate this kind of stuff? Is there an
> easier way of handling this type of code than using a domain model?
It's a portion of time ... but I accept that it isn't the majority of the
time (again, I'm not sure how to quantify it). The choice of Domain Model
(or not) is personal preference, but in my experience even (deceptively?)
simple CRUD stuff gets additional requirements once the customer has seen
the software, and I've always found Domain Model easier to extend once the
business rules (inevitably?) become more complex.
Cheers,
Richard
--------------------------------------------------
From: "Greg Young" <[email protected]>
Sent: Thursday, February 05, 2009 3:10 PM
To: <[email protected]>
Subject: [nhusers] Re: Should I use NHibernate+WCF?
>
> "My personal preference is to only create DTO classes when they are
> needed, hopefully saving time on creating both the DTO objects and the
> code to map my domain properties to them."
>
> Are you really saving *that* much time by taking on all the bad things
> that happen because of this?
>
> If it is a substantial portion of your time that would mean that you
> are heads down coding CRUD stuff by hand where typing speed becomes
> valuable? Could you code generate this kind of stuff? Is there an
> easier way of handling this type of code than using a domain model?
>
> Cheers,
>
> Greg
>
>
> On Thu, Feb 5, 2009 at 6:33 AM, Richard (Google)
> <[email protected]> wrote:
>>
>> Some thoughts on passing domain objects over WCF ...
>>
>> http://broloco.blogspot.com/2009/02/sending-domain-objects-across-wire.html
>>
>> Just my tuppence worth.
>>
>> Regards,
>> Richard
>>
>>
>>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"nhusers" 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/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---
