|
Title: Model and View Value Objects? Post by: Groady on August 19, 2009, 06:56:50 I'm wondering what is the 'best practice' for handling value objects in an application, specifically where they should be stored.
In the past I have kept value objects inside a directory named vo under my model directory (model/vo/). This makes sense to me as VO's are used to transport data from the model to somewhere else in the application. However I have a situation where I have one mediator which passes some 'view state' information as a VO to another mediator via a notification. Since this state data doesn't pass through the model tier should I create a separate vo directory under the view directory (view/vo/)? Or is it OK to simply continue using the currently structure of keeping all VO's in the model (model/vo/)? Title: Re: Model and View Value Objects? Post by: puremvc on August 20, 2009, 07:28:40 You can always create a view/vo package as well.
-=Cliff> |