Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought

Over 10 years of community discussion and knowledge are maintained here as a read-only archive.

New discussions should be taken up in issues on the appropriate projects at https://github.com/PureMVC

Pages: [1]
Author Topic: Model and View Value Objects?  (Read 7493 times)
Posts: 6

View Profile Email
« 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/)?
Global Moderator
Hero Member
Posts: 2871

View Profile WWW Email
« Reply #1 on: August 20, 2009, 07:28:40 »

You can always create a view/vo package as well.

Pages: [1]