basic question..

Firstly, let me apologise for posting such a basic question here, but since there isn't a users list it seems the only option.



After reviewing the source of the various examples I just wanted to clarify my understanding of one thing.



As far as I can tell in the examples, every time we handle a view event, we instantiate a new model object. Am I correct or have I overlooked something?



Assuming this is the case, what sort of performance impact should I expect for a high traffic application?



Perhaps it's because I have never done any swing development, but my understanding of the 'model' in MVC was more along the lines of the business model which has a life seperate from the user interface. In this case, when I look at the DiscRack app, I'm confused about the way the actually objects 'contained' in the model are retrieved within the event handler which then instantiates the model and passes in these objects.



I'm fairly certain that I'm right in saying that I could have a seperate model class which would provide the facility for the event class to specify the 'query' details without actually ever handling the data objects (I'm thinking of using Hibernate in this context). This would seem to me to give a better seperation of M from VC.



Again, sorry for bothering you all with my newbie questions.



Thanks,



Peter Whitfield 



ps. thanks for putting the effort in to build this framework - it looks excellent. I'm keen to trial it as an alternative to struts.

--

Barracuda mailing list

[email protected]

http://www.objectweb.org/wws/lists/projects/barracuda