http://davidlaing.com/2010/04/20/dtos-to-flatten-or-not-to-flatten/?utm_source=rss&utm_medium=rss&utm_campaign=dtos-to-flatten-or-not-to-flatten David Laing's thoughts on software development Tue, 07 Feb 2012 02:14:24 +0000 hourly 1 http://wordpress.org/?v=3.2.1 http://davidlaing.com/2010/04/20/dtos-to-flatten-or-not-to-flatten/#comment-17 OtherDavid Wed, 26 May 2010 22:45:17 +0000 http://davidlaing.com/?p=200#comment-17 Related - Why You Shouldn’t Expose Your Entities Through Your Services - http://davybrion.com/blog/2010/05/why-you-shouldnt-expose-your-entities-through-your-services/ Related – Why You Shouldn’t Expose Your Entities Through Your Services –
http://davybrion.com/blog/2010/05/why-you-shouldnt-expose-your-entities-through-your-services/

]]> http://davidlaing.com/2010/04/20/dtos-to-flatten-or-not-to-flatten/#comment-16 Hibri Thu, 22 Apr 2010 15:27:37 +0000 http://davidlaing.com/?p=200#comment-16 I would try to flatten it where possible, and try to avoid more than one dot. I think it makes discovery easier, for an API user. Interesting. I'm going to face this issue soon. It's how a consumer would use it. Maybe put yourself into the shoes of the API consumer ? Or get someone new to write something with the api I would try to flatten it where possible, and try to avoid more than
one dot. I think it makes discovery easier, for an API user.
Interesting. I’m going to face this issue soon.
It’s how a consumer would use it. Maybe put yourself into the shoes of
the API consumer ?
Or get someone new to write something with the api

]]>