title: Using MVC (Model View Controller) in a Client-Server architecture
body: <p>I'm trying to choose an design pattern for an application that I'm developing. The application is primarily based on a Client-Server architecture where the Client basically reads and writes data to the Server; its not a Web-application however, The client will have to install the software executable and then interact with a GUI in order to communicate with the Server (which exits on a different machine) through an internet protocol.</p>
  
  <p>Since the application is based on heavy interaction with a GUI, I was thinking about using the MVC design pattern, the thing is I'm having trouble deciding which part should exist on the Server and which on the Client side. In other words, is it ok to have the <strong>View</strong> (i.e the Boundary GUI classes and objects) and the <strong>Controller</strong> on the Client side, while leaving the <strong>Model</strong> (i.e the Entity objects) on the Server side; is this a viable or valid way of applying the MVC pattern ? Am I going in the right direction here ?
  Is this even possible ? I mean can those Boundary and Control classes operate and execute without having or accessing the Model classes on the same machine or process ?</p>
  
  <p>Should I have the whole thing (The Model, View and Controller classes) on the Client side and then just communicate with the Server database via the protocol ?</p>
  
  <p>Any suggestions or comments would be welcome.</p>