Dear all,

I'm working in a C# project and we are , in order to get some unity across the different parts of our UI, trying to use the MVC pattern. The client is windows form based and I'm trying to create a simple MVC pattern implementation.

It's been more challenging than expected, but I still have some questions regarding the MVC pattern. The problem comes mostly from the n-n relationships between its components: Here is what I've understood, but I'm not sure at all of it. Maybe someone can correct me?

• Model: can be shared among different Views. 1-n relationship between Model-View
• View: shows the state of the model. only one controller (can be shared among different views?). 1-1 relationship with the Model, 1-1 relationship with the controller
• Controller: handles the user actions on the view and updates the model. One controller can be shared among different views, a controller interacts only with one model?

I'm not sure about the two last ones:

• Can a view have several controller? Or can a view share a controller with another view? Or is it only a 1:1 relationship?
• Can a controller handle several views? can it interact with several models?

Also, I take advantage of this question to ask another MVC related question. I've suppressed all the synchronous calls between the different members of the MVC, making use of the events and delegates. One last call is still synchronous and is actually the most important one: The call between the view and the controller is still synchronous, as I need to know rather the controller has been able to handle the user's action or not. This is very bad as it means that I could block the UI thread (hence the client itself) while the controller is processing or doing some work. How can I avoid this? I can make use of the callback but then how do i know to which event the callback comes from?

PS: I can't change the pattern at this stage, so please avoid answers of type "use MVP or MVVC, etc ;)

Thanks!

Dear all,

I'm working in a C# project and we are , in order to get some unity across the different parts of our UI, trying to use the MVC pattern. The client is windows form based and I'm trying to create a simple MVC pattern implementation.

It's been more challenging than expected, but I still have some questions regarding the MVC pattern. The problem comes mostly from the n-n relationships between its components: Here is what I've understood, but I'm not sure at all of it. Maybe someone can correct me?

• Model: can be shared among different Views. 1-n relationship between Model-View
• View: shows the state of the model. only one controller (can be shared among different views?). 1-1 relationship with the Model, 1-1 relationship with the controller
• Controller: handles the user actions on the view and updates the model. One controller can be shared among different views, a controller interacts only with one model?

I'm not sure about the two last ones:

• Can a view have several controller? Or can a view share a controller with another view? Or is it only a 1:1 relationship?
• Can a controller handle several views? can it interact with several models?

Also, I take advantage of this question to ask another MVC related question. I've suppressed all the synchronous calls between the different members of the MVC, making use of the events and delegates. One last call is still synchronous and is actually the most important one: The call between the view and the controller is still synchronous, as I need to know rather the controller has been able to handle the user's action or not. This is very bad as it means that I could block the UI thread (hence the client itself) while the controller is processing or doing some work. How can I avoid this? I can make use of the callback but then how do i know to which event the callback comes from?

PS: I can't change the pattern at this stage, so please avoid answers of type "use MVP or MVVC, etc ;)

Thanks!