MVC 1 vs MVC 2
MVC 1 과 MVC 2 의 차이를 구조화된 비교 표에서 확인한 뒤, 관련 면접 질문, 퀴즈, 유사 비교로 이어가세요.
차이점 비교
MVC 1 vs MVC 2 - A key comparison and difference of the topics or subjects that will help you understand which is best for your use case. Check out to compare MVC 2 and MVC 1 as very common job interview questions.
MVC 1 과 MVC 2 의 차이
MVC 1 vs MVC 2 - A key comparison and difference of the topics or subjects that will help you understand which is best for your use case. Check out to compare MVC 2 and MVC 1 as very common job interview questions.
|
MVC 1
|
MVC 2
|
|---|---|
| In MVC1, only one component is responsible for receiving request and sending response. | In MVC2, there is separate components for receiving and sending response. i.e. Controller & View. |
| MVC1 associates the presentation logic with the business logic. | MVC 2 isolates or disassociates the presentation logic from business logic. |
| In MVC 1, business logic and presentation Logic is combined so web designer and web developer cant work simulateously. | Since both logics are separate that's why designer and developer can work together. |
| Doesn't support reusability of application components. | Reusability of components. |
| In MVC 1, controller and model,both are JSP. | While controller is servlet and model is java class. |
| In MVC1 there is tight coupling between page and model as data access is usually done using Custom tag or through java bean call. | In MVC2 architecture there is only one controller which receives all the request for the application and is responsible for taking appropriate action in response to each request. |
복습용 저장
이 항목을 북마크하거나, 어렵게 표시하거나, 복습 세트에 넣을 수 있습니다.
관련 차이점
MVC 1 및 MVC 2 와 관련된 유사 비교를 살펴보며 더 넓은 맥락과 면접 준비에 도움을 얻어보세요.
아래에서 차이점 보기
아래의 모든 주제 비교를 살펴보거나, 위 검색창을 사용해 목록을 즉시 좁혀보세요.