Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Why do we need client side MVC?

 
Ranch Hand
Posts: 240
2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a few questions to ask, your help will be much appreciated.
What is MVC at client side? does it mean MVC implemented within a View page?
I want to know which MVC structure is right, I am confused between the two that I have been taught by my trainer and the one i find on internet. Please refer the attachments i added
What is the advantage or why do we need client side MVC?

I had posted this question on AngularJS forum 2 weeks ago but i didnt get any reply.

Thanks.
MVC-architecture-that-i-found-on-internet.png
[Thumbnail for MVC-architecture-that-i-found-on-internet.png]
MVC-architecture-that-my-trainer-taught.jpg
[Thumbnail for MVC-architecture-that-my-trainer-taught.jpg]
 
Rancher
Posts: 1170
18
IntelliJ IDE Hibernate Firefox Browser MySQL Database Spring Tomcat Server Java
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
MVC supports rapid and parallel development. With MVC, one programmer can work on the view while other can work on the controller to create business logic of the web application.
The application developed using MVC can be three times faster than application developed using other development patterns.
In the MVC Model, you can create multiple views for a model. Code duplication is very limited in MVC because it separates data and business logic from the display.
MVC also supports asynchronous technique, which helps developers to develop an application that loads very fast and modification does not affect the entire model because model part does not depend on the views part.
Therefore, any changes in the Model will not affect the entire architecture.
The MVC pattern returns data without applying any formatting so the same components can be used and called for use with any interface.
Using this platform, it is very easy to develop SEO-friendly URLs to generate more visits from a specific application.
 
Bartender
Posts: 322
24
Eclipse IDE Firefox Browser
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don’t believe the first screenshot is MVC. That looks more like MVP (Model View Presenter). In MVP, the Presenter is both Active View and Controller (while the V in MVP is an interface View).

MVP is a derivative of MVC used in .NET apps. I’ve had to use it in C# with Window Form apps, but never seen it used in Java. At least in my experience, MVP can lead to code duplication as each Windows Form is siloed from other Windows Forms.
 
The glass is neither half full or half empty. It is too big. But this tiny ad is just right:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
    Bookmark Topic Watch Topic
  • New Topic