A further consideration is whether or not you will need any form of synchronisation between objects on the client-side. For instance, if a change in a Person's phone number needs to be instantly reflected on all the open screens in your application, then you need some sort of co-ordinating layer on the client.
On Mar 6, 5:02 pm, Greg Young <[email protected]> wrote: > I would personally recommend something slightly different here as > there can be quite a few issues with this architecture.. > > > Data Tier: > > DAL > > Data WCF Service > > Dto --> > > > --------- boundary -------------- > > > Presentation Tier > > Maybe a presentation model ... > > Presentation > > Then for writes ... > > > Presentation Tier > > Presentation > > Maybe a presentation model > > Commands ... > > ---boudary ---- > Message Handlers > Domain > Repository > DAL > > I did a talk on some of this for the Euro Van recently here is a > linkhttp://vimeo.com/3171910 > > Cheers, > > Greg > > > > On Fri, Mar 6, 2009 at 11:49 AM, Tommaso Caldarola <[email protected]> > wrote: > > > the answer is: send what you must use, namely DTOs > > > Data Tier: > > DAL > > Repository > > Data WCF Service > > Dto --> > > > --------- boundary -------------- > > > Presentation Tier > > --> Dto > > Data WCF Proxy > > Repository > > Business > > Presentation > > > tommaso > > > On 6 Mar, 11:06, Chucara <[email protected]> wrote: > >> I've found several threads here and elsewhere concerning this issue, > >> so I know I'm not the only one who've run into it. Still, there are a > >> few things I don't fully understand, so I'll ask them here. > > >> I am using nHibernate in a multitiered environment. I'm using WCF to > >> serialize the POCO objects I'm creating with nHibernate. This fails as > >> WCF apparently tries to make nHibernate lazy load data after the > >> session has closed. > > >> I've tried to set lazy and outer-join like so: > >> <many-to-one name="DeliveryAddress" column="ACT_DELIV_ADR" > >> class="DeliveryAddress" outer-join="true" lazy="false"/> > > >> However, this seems to make nHibernate make several calls to load the > >> data, which is extremely slow. > > >> My question is: How can I completely disable lazy loading and proxy > >> objects? And how can I load this eagerly in one call rather than the > >> ineffective solution I have now? > > >> We will manually handle loading, and we need type sharing between the > >> client and the the server as well as behavior in the model classes. > > -- > It is the mark of an educated mind to be able to entertain a thought > without accepting it. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
