WO2002006956A2 - Architecture modele-vue-controleur-client utilisee dans une application logicielle de donnees distribuees - Google Patents
Architecture modele-vue-controleur-client utilisee dans une application logicielle de donnees distribuees Download PDFInfo
- Publication number
- WO2002006956A2 WO2002006956A2 PCT/US2001/041365 US0141365W WO0206956A2 WO 2002006956 A2 WO2002006956 A2 WO 2002006956A2 US 0141365 W US0141365 W US 0141365W WO 0206956 A2 WO0206956 A2 WO 0206956A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- component
- model
- client
- view
- controller
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
Definitions
- each view 52 can be associated with the model 51 , and can register with the change-propagation mechanism 54. Additionally, each view can create a corresponding controller 53. Typically there is one-to-one relationship between views 52 and controllers 53. Views
- the model 51 in the MVC architecture both encapsulates the core data 55 and contains business logic for accessing and updating the source data of the core data 55 values.
- the model 51 must be modified to reflect those changes in the core data 55, potentially causing further change requirements in view and controllers.
- This limitation can become further compounded in enterprise-wide business application development. Specifically, in client-server applications, often distributed business objects are required to process state changes in the core data 55.
- MVC-client can include at least one model component, at least one view component, at least one controller component and at least one client component can be provided.
- the client component encapsulates business logic for responding to service requests from a corresponding controller component. Responsive to the service requests, the client component can execute the business logic and communicate with business objects in the distributed data software application.
- the client component can provide to the corresponding model component state changes for storage in the model component. Notably, the client can exclusively encapsulate the business logic.
- a typical node 2 can include a server computer 5 and a client computer 6 connected in a local area network (LAN).
- LAN local area network
- a node 2 is not limited in this regard. Rather, a node 2 can consist of as little as a server computer 5. Still, typically a node 2 can include both one or more servers 5 and a plurality of client computers 6. The server computer 5 and the client computer 6 can be operatively connected in the LAN through a hub 7. Finally, the entire node 2 can be connected to the WAN 3 through a router 8 or other suitable switching means, for example a bridge or gateway.
- Each of the server computers 5 and the client computers 6 can include a central processing unit (CPU) 10, network interface circuitry 13, for example an Ethernet network interface card, fixed storage 12, for example a hard disk drive, and an internal memory device 1 1 , for example random access memory 1 1 .
- Each of the server computers 5 and the client computers 6 can include a keyboard 14, and at least one user interface display unit 15 such as a video data terminal (VDT) operatively connected thereto.
- VDT video data terminal
- FIG. 4 is a UML diagram of MVC-Client deployed on the distributed data network of Figure 1.
- an object-oriented implementation of MVC-Client preferably includes a separate class for each component.
- Components included in MVC-Client include at least one model component 151 , at least one view component 152, at least one controller component 153 corresponding to the view component 152, and at least one client component 161 corresponding to the controller component 153.
- a change-propagation mechanism 154 can further be provided in order to maintain a registry 160 of dependent view and controller components 152,
- Changes to the state of the model 151 preferably trigger the change- propagation mechanism 154.
- view components 1 52 and selected controller components 153 can register with the change-propagation mechanism 154 in order to express a need to be informed about changes to core data 1 55 stored within the model 151 .
- the change-propagation mechanism 154 preferably is the only link between the model 151 and the views 152 and controllers 153. Notably, the change-propagation mechanism
- view components 152 can present the core data 155 to the user in a user interface.
- Different view components 152 can present the core data 155 of the model 151 in different ways.
- each view component 152 preferably defines an update procedure 158 specified in the change propagation mechanism 154 that can be activated by the change- propagation mechanism 154.
- the view component 152 can retrieve from the model component 151 the current core data 155 values to be displayed to the user in the user interface. Subsequently, the view component 152 can display the core data 155 to the user in the user interface.
- each view component 152 can be associated with the model component 1 51 , and can register with the change- propagation mechanism 154.
- view components 152 preferably can allow associated controller components 1 53 to directly manipulate the displaying of the core data 155 in the user interface without requesting user interface servicing from the model component 151.
- the controller component 153 can handle user- triggered user interface operations that do not affect the model 151 , for instance scrolling.
- Controller components 1 53 can accept user inputs as events. Although the delivery of these events to a controller 153 can depend on the user interface platform, traditionally, these events can be handled in an event- handling procedure implemented in each controller 1 53 which can be called for each relevant event. Events can be translated into requests for the client 160, the model 151 or the associated view 152. If the behavior of a controller 1 53 depends on the state of the model 151 , the controller 153 can register with the change-propagation mechanism 154 and, like the view component 152, the controller 153 can implement an update procedure 159. During instantiation, the controller component 153 can accept an association with a corresponding model component 151 , view component 152 and a client component 161 .
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| AU2001276053A AU2001276053A1 (en) | 2000-07-19 | 2001-07-13 | Model-view-controller-client architecture for use in a distributed data softwareapplication |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US61900700A | 2000-07-19 | 2000-07-19 | |
| US09/619,007 | 2000-07-19 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| WO2002006956A2 true WO2002006956A2 (fr) | 2002-01-24 |
| WO2002006956A3 WO2002006956A3 (fr) | 2002-03-21 |
Family
ID=24480053
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/US2001/041365 Ceased WO2002006956A2 (fr) | 2000-07-19 | 2001-07-13 | Architecture modele-vue-controleur-client utilisee dans une application logicielle de donnees distribuees |
Country Status (2)
| Country | Link |
|---|---|
| AU (1) | AU2001276053A1 (fr) |
| WO (1) | WO2002006956A2 (fr) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1376337A1 (fr) * | 2002-06-12 | 2004-01-02 | Commerce One Operations, Inc. | Action/commande/cadre d'application d'objets d'affaires |
| US7917893B2 (en) | 2007-03-07 | 2011-03-29 | Microsoft Corporation | Using a system of annotations to generate views and adapters |
| US8219654B2 (en) | 2007-05-17 | 2012-07-10 | Microsoft Corporation | Highly available central controller to store and enforce valid state transitions of distributed components |
| CN111930822A (zh) * | 2020-09-11 | 2020-11-13 | 山东钢铁集团日照有限公司 | 一种异步分布式信息协同控制的软件构架装置及方法 |
| CN112527773A (zh) * | 2020-12-14 | 2021-03-19 | 成都炽娱互动科技有限公司 | 一种基于dbvc框架的数据模型、视图标准化方法及系统 |
-
2001
- 2001-07-13 WO PCT/US2001/041365 patent/WO2002006956A2/fr not_active Ceased
- 2001-07-13 AU AU2001276053A patent/AU2001276053A1/en not_active Abandoned
Non-Patent Citations (6)
| Title |
|---|
| August 1997, TEMPLATE SOFTWARE, DEVELOPMENT A WFT WORKFLOW SYSTEM * |
| August 1997, TEMPLATE SOFTWARE, SNAP PROGRAMMING LANGUAGE, USER'S GUIDE DEVELOPMENT PROCESS MANUAL * |
| August 1997, TEMPLATE SOFTWARE, WORKFLOW TEMPLATE, USING THE WFT DEVELOPMENT ENVIRONMENT * |
| November 1996, RATIONAL SOFTWARE CORPORATION, RATIONAL ROSE 4.0, ROUND TRIP ENGINEERING WITH RATIONAL ROSE/C++ * |
| November 1996, RATIONAL SOFTWARE CORPORATION, RATIONAL ROSE 4.0, USING RATIONAL ROSE 4.0 * |
| November 1996, RATIONAL SOFTWARE CORPORATION, UNIFIED MODELING LANGUAGE, BOOCH & OMT QUICK REFERENCE GUIDE * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1376337A1 (fr) * | 2002-06-12 | 2004-01-02 | Commerce One Operations, Inc. | Action/commande/cadre d'application d'objets d'affaires |
| US7917893B2 (en) | 2007-03-07 | 2011-03-29 | Microsoft Corporation | Using a system of annotations to generate views and adapters |
| US8219654B2 (en) | 2007-05-17 | 2012-07-10 | Microsoft Corporation | Highly available central controller to store and enforce valid state transitions of distributed components |
| CN111930822A (zh) * | 2020-09-11 | 2020-11-13 | 山东钢铁集团日照有限公司 | 一种异步分布式信息协同控制的软件构架装置及方法 |
| CN112527773A (zh) * | 2020-12-14 | 2021-03-19 | 成都炽娱互动科技有限公司 | 一种基于dbvc框架的数据模型、视图标准化方法及系统 |
| CN112527773B (zh) * | 2020-12-14 | 2024-09-24 | 成都炽娱互动科技有限公司 | 一种基于dbvc框架的数据模型、视图标准化方法及系统 |
Also Published As
| Publication number | Publication date |
|---|---|
| AU2001276053A1 (en) | 2002-01-30 |
| WO2002006956A3 (fr) | 2002-03-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US5893106A (en) | Object oriented server process framework with interdependent-object creation | |
| US6148323A (en) | System and method for managing the execution of system management | |
| Bruneton et al. | Recursive and dynamic software composition with sharing | |
| Buschmann et al. | Pattern-oriented Software Architecture: a Pattern Language for Distributed Computing, Volume 4 | |
| US5949998A (en) | Filtering an object interface definition to determine services needed and provided | |
| US20020078255A1 (en) | Pluggable instantiable distributed objects | |
| EP0912014B1 (fr) | Procédé, appareil et programme pour accès à un service d' information de gestion sur un serveur | |
| US5758351A (en) | System and method for the creation and use of surrogate information system objects | |
| Yang et al. | CORBA: a platform for distributed object computing | |
| US5903754A (en) | Dynamic layered protocol stack | |
| US7174361B1 (en) | Scripting task-level user-interfaces | |
| US20040205525A1 (en) | Automatic identification of form contents | |
| JPH11242605A (ja) | マルチスレッドのクライアント・ベースapiをシングルスレッドのサーバ・ベースapiにインタフェースさせる方法、装置、およびプログラム製品 | |
| EP0924617A2 (fr) | Procédé et appareil pour l'exécution de code pendant l'invocation d'une fonction d'objet | |
| EP0924614A2 (fr) | Procédé et appareil pour la représentation efficace des identificateurs à longueur variable dans un système d'objets distribués | |
| KR100370548B1 (ko) | 임베디드 시스템의 통합 소프트웨어 개발 프레임워크를제공하는 실시간 미들웨어 장치 및 그 서비스 방법 | |
| WO2000058873A1 (fr) | Moteur de conception du flux des travaux | |
| Gomaa et al. | Reusable component interconnection patterns for distributed software architectures | |
| WO2002006956A2 (fr) | Architecture modele-vue-controleur-client utilisee dans une application logicielle de donnees distribuees | |
| McArthur et al. | An evaluation of the impact of component-based architectures on software reusability | |
| Henning | Massively Multiplayer Middleware: Building scaleable middleware for ultra-massive online games teaches a lesson we all can use: Big project, simple design. | |
| US9049044B1 (en) | Method of management and distribution of device adapters for element management systems | |
| Sengul et al. | Building a service provisioning system using the Enterprise JavaBean framework | |
| Pautet et al. | GLADE users guide | |
| Arregui et al. | Rule-based transactional object migration over a reflective middleware |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW |
|
| AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
| AK | Designated states |
Kind code of ref document: A3 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW |
|
| AL | Designated countries for regional patents |
Kind code of ref document: A3 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
| DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
| REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
| 32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: COMMUNICATION UNDER RULE 69(1) (EPO FORM 1205A) OF 17.06.2003 |
|
| 122 | Ep: pct application non-entry in european phase | ||
| NENP | Non-entry into the national phase in: |
Ref country code: JP |