• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

web and GUI client design

 
Gabriel Belingueres
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

In a previous post I've seen this link to support web and application clients:

http://java.sun.com/blueprints/guidelines/designing_enterprise_applications/client_tier/multiple_types/index.html#1028399

Now, I been reading it and I think it is kind of a heavy weight design.

I would like to know your opinion about this design for supporting multiple clients, versus a simpler one based on a business delegate pattern, where every kind of client is coded from scratch and you only reuse business logic.

Gabriel
 
Francesco Bianchi
Ranch Hand
Posts: 62
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As stated also in HFSJ, MVC pattern is kind-of extension of business delegate pattern in the sense that uses the same principles, have the same benefits but adds much more flexibility on the navigation side in change of increased development costs.

In general, there is not a best choice: it depends in fact on the use cases you collected by your users.

If talking about both web and application clients, I think that MVC is a safer choice. Web and client applications are very different regarding the way they can communicate with a server, I would say almost the opposite. You cannot be sure that the methods implemented having the web model in mind can work correctly if piloted by an application client.

To make the 2 models act in a reasonably similar way you should add so much overhead that you could lose the benefits of a lighter model as business delegate.

Moreover MVC let's you control navigation on the server side while a simple Business Delegate just has to wait for a request forcing you to put all the navigation logic on the clients.

At least, in my opinion
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic