Yes, Fabio. I am researchin to clear my mind, but I have got the picture of what we must do. You all was very helpfull. We will do the homework now and we will publish the results. We are, by now, storing in the session and doing the merge. But we will change to the first option and analyse each case to think what to do. Now we have a good base to start over.
Thanks a lot. On 1 jun, 17:26, Fabio Maulo <[email protected]> wrote: > 2009/6/1 Jason Meckley <[email protected]> > > > > > I have only required the first suggestion of building up a dto. I > > haven't had a need to store domain objects in session. > > Sure Jason... the matter is that the real answer is : "it depend". > When you have a lot of use cases, that span in more than one request, to use > DTOs mean rewrite DTOs almost for everything. > Guga is looking for a certain recipe but there is not a real/certain one > because there are a lot of variables (from use-cases to amount of users, > where the application will be run, development-team's capability and so on). > -- > Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
