[go: up one dir, main page]

CN109032587B - Data stream management framework, method, terminal equipment and storage medium - Google Patents

Data stream management framework, method, terminal equipment and storage medium Download PDF

Info

Publication number
CN109032587B
CN109032587B CN201810796198.7A CN201810796198A CN109032587B CN 109032587 B CN109032587 B CN 109032587B CN 201810796198 A CN201810796198 A CN 201810796198A CN 109032587 B CN109032587 B CN 109032587B
Authority
CN
China
Prior art keywords
data
view
component
field
observable
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.)
Active
Application number
CN201810796198.7A
Other languages
Chinese (zh)
Other versions
CN109032587A (en
Inventor
索传良
张文明
陈少杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ningbo Jingda Technology Co ltd
Original Assignee
Wuhan Douyu Network Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Wuhan Douyu Network Technology Co Ltd filed Critical Wuhan Douyu Network Technology Co Ltd
Priority to CN201810796198.7A priority Critical patent/CN109032587B/en
Publication of CN109032587A publication Critical patent/CN109032587A/en
Application granted granted Critical
Publication of CN109032587B publication Critical patent/CN109032587B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/34Graphical or visual programming
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本发明公开了一种数据流管理框架、方法、终端设备及存储介质,适用于应用开发领域。本发明提供的框架包括:存储组件:用于提供一个单例模式的数据存储对象和一个可观察对象,所述数据存储对象用于存储数据流中数据,所述可观察对象用于控制视图的刷新;视图组件:用于订阅可观察对象,当检测到被观察字段与初始字段相同时,调用强制更新方法刷新视图;控制组件:用于接收传入的更新数据,合并所述更新数据和当前数据后,调用所述可观察对象多播发生数据变更的键值;服务组件:用于将请求获得的数据进行请求逻辑与业务逻辑分离。本发明减少了代码的冗余,同时,使得组件间数据传递过程可见,便于代码调试。

Figure 201810796198

The invention discloses a data flow management framework, a method, a terminal device and a storage medium, which are suitable for the application development field. The framework provided by the present invention includes: a storage component: a data storage object for providing a singleton pattern and an observable object, the data storage object is used to store data in the data stream, and the observable object is used to control the view Refresh; view component: used to subscribe to the observable object, when it is detected that the observed field is the same as the initial field, call the forced update method to refresh the view; control component: used to receive the incoming update data, merge the update data with the current After the data is obtained, the observable object is called to multicast the key value of the data change; service component: used to separate the request logic from the business logic for the data obtained by the request. The invention reduces the redundancy of the code, and at the same time, makes the data transfer process between the components visible, which is convenient for code debugging.

Figure 201810796198

Description

Data stream management framework, method, terminal equipment and storage medium
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a data stream management framework, a data stream management method, a terminal device, and a storage medium.
Background
Js is one of mainstream frameworks developed at the front end, the framework can well solve the view rendering problem as a view layer, but because of lack of effective state management, the framework is weak when a large-scale front-end application is constructed, and a state management framework needs to be specially introduced for better managing and debugging components therein.
At present, common state management methods include Redox and mobx, and when a Redox architecture is used, a large amount of template codes are needed for realizing each function, so that code redundancy can reduce development efficiency. And the Mobx architecture is used, so that the data transmission process between the storage component and other components is invisible, and debugging is difficult.
Therefore, it is necessary to provide a framework with less redundant codes and visible data transmission process.
Disclosure of Invention
In view of this, embodiments of the present invention provide a data stream management framework, a method, a terminal device, and a storage medium, so as to solve the problem that codes of an existing management framework are redundant or difficult to debug.
In a first aspect of the embodiments of the present invention, a data stream management framework is provided, including:
a storage component: a data storage object for providing a singleton schema and an observable object, the data storage object for storing data in a data stream, the observable object for controlling refreshing of a view;
view component: the component DIdMount method is used for subscribing the observable object in the component DIdMount method of the PureComponent component lifecycle, and calling a forced update method to refresh the view when the observed field is detected to be the same as the initial field;
a control component: the field is used for receiving incoming updating data, acquiring current data in the data storage object, merging the updating data and the current data, and calling the observable object to multicast the field with data change;
a service component: the interface data is used for defining the interface data of the request server side, and the request logic and the service logic of the data obtained by the request are separated.
In a second aspect of the embodiments of the present invention, a method for managing data stream is provided, including:
in the singleton mode, a data storage object is created, and an observable object is defined in the data storage object, wherein the data storage object is used for storing data in a data stream;
after the view is rendered for the first time, subscribing the observable object in a componentDIdMount method of the PureComponent component life cycle by the current view;
when receiving the updated data, acquiring the current data in the data storage object, merging the updated data and the current data, and calling the field of the observable object multicast with data change;
and when the field with the data change is the same as the initial field of the view, calling a forced updating method to refresh the current view.
In a third aspect of the embodiments of the present invention, there is provided a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the framework according to the first aspect of the embodiments of the present invention when executing the computer program.
In a fourth aspect of the embodiments of the present invention, a computer-readable storage medium is provided, where a computer program is stored, and the computer program, when executed by a processor, implements the framework provided in the first aspect of the embodiments of the present invention.
In a fifth aspect of embodiments of the present invention, a computer program product is provided, the computer program product comprising a computer program that, when executed by one or more processors, performs the steps of the method provided in the first aspect of embodiments of the present invention.
In the embodiment of the invention, the control component and the view component are bound through the unique identification field, when data is updated, the identification field of the multicast change of the observable object is forced to refresh the corresponding view according to the identification field. Meanwhile, based on observable objects, a control module and a view module can be separated, data is transmitted through a store, so that the transmission process is visible, and code debugging is facilitated.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
FIG. 1 is a schematic structural diagram of a data stream management framework according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of another structure of a data stream management framework according to a second embodiment of the present invention;
fig. 3 is a schematic flow chart of a data stream management method according to a third embodiment of the present invention;
fig. 4 is a schematic structural diagram of a terminal device according to an embodiment of the present invention;
Detailed Description
The embodiment of the invention provides a data stream management framework, a data stream management method, terminal equipment and a storage medium, which are used for managing data streams in a view updating process.
In order to make the objects, features and advantages of the present invention more obvious and understandable, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the embodiments described below are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The first embodiment is as follows:
referring to fig. 1, a schematic structural diagram of a data stream management framework according to an embodiment of the present invention includes components:
the storage component 110: a data storage object for providing a singleton schema and an observable object, the data storage object for storing data in a data stream, the observable object for controlling refreshing of a view;
the singleton mode is that the data storage class only has one object instance, and under the singleton mode, only one object is ensured to manage and update data, so that data confusion caused by multiple objects is avoided. Specifically, the present module, i.e. the data storage class interface, is output externally, and data is initialized in the constructor of the class, and an instance object is initialized and returned.
The observable object is a special observer type and can push a value to a plurality of observers in a multi-path mode. Preferably, the observable object can observe the data change and can be used as an observed object to transmit the change data.
Optionally, a data registration method and a data acquisition method are defined in the storage component. Updated data stream data is acquired in the storage component, and the data stream data is registered and stored.
View component 120: the component DIdMount method is used for subscribing the observable object in the component DIdMount method of the PureComponent component lifecycle, and calling a forced update method to refresh the view when the observed field is detected to be the same as the initial field;
the PureComponent component is an optimized React application method, and can reduce view rendering times by shallow comparison of the programs and the state. When it detects that the state or the prop changes, it calls render method to render.
The componentDIdMount method can access the observable in the storage component after initializing the render, and can receive the variation data multicast by subscribing to the observable.
Receiving a change field of the multicast of the observable object in the componentDIdMount method, and calling a forceupdate method to forcibly update the corresponding view when the change field is consistent with the field in the view.
Optionally, the view component is initialized, a unique mapping field in the control component corresponding to the view is injected into a constructor of the view component, and initialization data of the control component is injected. The unique mapping field is a self-defined view identifier, can be used for identifying a view and can be represented as a key for updating data, and when the data is changed, the changed field is informed, so that the changed data and the corresponding view can be obtained.
Optionally, when the view component is destroyed, the subscription of the observable object is cancelled.
The control assembly 130: the field is used for receiving incoming updating data, acquiring current data in the data storage object, merging the updating data and the current data, and calling the observable object to multicast the field with data change;
the updating data is the updating data which is received by the background and sent by the server side. And when the data storage object updates data every time, the current latest data can be stored, and the corresponding latest data can be found according to the mapping field. By combining the latest data and the updated data, the updated latest data can be obtained, and the updated latest data can directly cover the original data, so that the view updating operation is realized.
In the data storage component, the observable may multicast to the subscribers the changed fields, i.e., the key values of the data changes, after receiving the data change information.
The service component 140: the interface data is used for defining the interface data of the request server side, and the request logic and the service logic of the data obtained by the request are separated.
After the view page requests the server for the latest data, the request data returned by the server is received, the request data content and the service data in the request data are obtained by an interface definition method, and the two parts of data are separated, so that the service data can be directly used conveniently.
Optionally, page level interface data is intercepted.
And the control component and the view component are bound through the unique mapping field, and the observable object multicast change field is utilized to control the corresponding view refreshing. The view updating logic is greatly simplified, the data transmission and the component relation are clear and visible, and the debugging is convenient.
Example two:
on the basis of fig. 1, details of a data delivery process of each component in the data stream management framework are described in conjunction with fig. 2, specifically as follows:
the Service component 20 is a Service program running in the background and has no user interface. Other components can be bound for data interaction or communication with the server. In the Service component 20, the update data is requested through the request interface data module 201, and the separation of the request logic with side effect from the Service logic is realized by defining the server-side interface data. Optionally, a page-level interface interception function is provided.
The Controller component 21 is generally used to collect, validate request parameters and bind command objects, and to hand the command objects to the business process logic. In the embodiment of the present invention, the Controller component 21 is mainly used for acquiring the update data and controlling the view refresh. Specifically, the View in the View component 22 is bound in the create mapping field key module 211, and initialization data is injected for the construction method 221 of the constructor in the View component 22. In the constructor of the View component 22, each View generated is bound with a unique mapping field, which has a sequence string, usually customized, generated by the Controller component 21.
When the View component 22 processes rendering, it will obtain initialization data in the store component 23, and render the View for the first time according to the initialization data. The View component 22, i.e., the View component, contains all the interface display elements, such as text, drawings, pictures, web pages, etc. Each view is bound with a unique mapping field key.
When rendering the view, the Controller component 21 learns the updated fields from the obtained updated data, informs the observable 232 through the update logic module 213, and multicasts the changed fields by the observable 232. In the update logic module 213 of the Controller component 21, the storage data in the Store component 23 is also obtained, the old and new data are merged, and the observable object is called to multicast the key value of the changed data.
In the View component 22, after the initial rendering is completed, the observable objects 232 in the store component 23 are subscribed to in the componentDIdMount method of its lifecycle. When data multicast by the observable 232 is received and the presence of a view with the same field is detected, a forceupdate method is called to force the view to be refreshed.
The store component 23 is generally configured to store data stream data, which is view display data of a view included in the current view component 22, specifically, a singleton object for data storage. The data attribute is used to store data stream data in the data storage module 231 and the observable object 232 is an instance of the BehaviorSubject class. Optionally, the store component 23 further includes a data registration method register and a data obtaining method getDate.
After the update logic module 213 in the Controller component 21 obtains the update data of the Service component 20, it will read the current data from the data storage module 231, and merge the update data and the current data, for example, merge through the assign method in lodashh. After the change field is broadcasted by the observable object, the merged data can be used for rendering.
When the View component 22 is destroyed, subscriptions for observable objects in the Store component should also be canceled.
Compared with the reduce, when a plurality of states need to be managed, the reduce combination is needed to generate a new state to change the original state every time an action is generated, and for some actions with more functional requirements, a large amount of redundant codes are generated because the states are managed. In the application, the corresponding view can be directly updated by informing the field (informing the state change) of the changed data through the observable object, the logic is simple and clear, and the code amount is reduced.
Example three:
a data stream management framework has been mainly described above, and a data stream management method will be described in detail below.
Fig. 3 shows a schematic structural diagram of a data stream management method, including:
s301, under a singleton mode, creating a data storage object, and defining an observable object in the data storage object, wherein the data storage object is used for storing data in a data stream;
in the embodiment of the present invention, the observable object may monitor the change field of the occurrence data, or may be used as an observed object person, which is monitored by the view component.
Optionally, a data registration method and a data acquisition method are defined in the data storage object. In the data storage object, the update data is required to be acquired, and the update data is registered and stored according to the category, for example, the data is stored according to the key value corresponding relation.
S302, after the view is rendered for the first time, subscribing the observable object in a componentDIdMount method of the PureComponent component life cycle by the current view;
when the view is rendered for the first time, a unique mapping field is bound for the view, so that each update can update the corresponding view according to the field. The componentDIdMount method may subscribe to an event, and when the event is triggered, the view may make corresponding feedback, such as an update operation.
Optionally, the view is initialized, a unique mapping field corresponding to the view is injected into a constructor of the view, and initialization data is injected into the view.
Optionally, when the view component is destroyed, the subscription of the observable object is cancelled.
S303, after receiving the updated data, acquiring the current data in the data storage object, merging the updated data and the current data, and calling the field of the observable object multicast with data change;
the updating of the view needs to request the latest data of the server through the background, the data of the server end received by the interface are disordered and mixed, and the request data and the service data are separated through a definition method. Optionally, page level interface data is intercepted.
And S304, when the field with the data change is the same as the initial field of the view, calling a forced updating method to refresh the current view.
The initial field is a unique mapping field bound for rendering the view when the view is rendered for the first time.
Example four:
fig. 4 is a schematic diagram of a terminal device structure for managing data stream according to an embodiment of the present invention. The terminal device is a mobile computer device with a touch screen, and includes but is not limited to a smart phone, a smart watch, a notebook, a tablet computer, a POS machine, and even a vehicle-mounted computer. As shown in fig. 4, the terminal device 4 of this embodiment includes: a memory 410, a processor 420, and a system bus 430, the memory 410 including executable programs 4101 stored thereon, it being understood by those skilled in the art that the terminal device structure shown in fig. 4 does not constitute a limitation of the terminal device and may include more or fewer components than shown, or some components may be combined, or a different arrangement of components.
The following specifically describes each constituent component of the terminal device with reference to fig. 4:
the memory 410 may be used to store software programs and modules, and the processor 420 performs various functional applications of the terminal and data processing by operating the software programs and modules stored in the memory 410. The memory 410 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the terminal device, and the like. Further, the memory 410 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
The executable program 4101 of the network performance parameter collection method is contained in the memory 410, and the executable program 4101 may be divided into one or more modules/units, which are stored in the memory 410 and executed by the processor 420 to complete the transmission of the notification and obtain the notification implementation process, and may be a series of computer program instruction segments capable of performing specific functions, and the instruction segments are used for describing the execution process of the computer program 4101 in the terminal device 4. For example, the computer programs 4101 may be various components of a data stream management framework.
The processor 420 is a control center of the terminal device, connects various parts of the entire terminal device using various interfaces and lines, performs various functions of the terminal and processes data by operating or executing software programs and/or modules stored in the memory 410 and calling data stored in the memory 410, thereby integrally monitoring the terminal. Alternatively, processor 420 may include one or more processing units; preferably, the processor 420 may integrate an application processor, which mainly handles operating systems, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 420.
The system bus 430 is used to connect functional units inside the computer, and can transmit data information, address information, and control information, and may be, for example, a PCI bus, an ISA bus, a VESA bus, etc. The instructions of the processor 420 are transmitted to the memory 410 through the bus, the memory 410 feeds data back to the processor 420, and the system bus 430 is responsible for data and instruction interaction between the processor 420 and the memory 410. Of course, the system bus 430 may also access other devices such as network interfaces, display devices, and the like.
The terminal device at least includes a CPU, a chipset, a memory, a disk system, and the like, and other components are not described herein again.
In this embodiment of the present invention, the executable program executed by the processor 420 included in the terminal device specifically includes:
a method of data stream management, comprising:
in the singleton mode, a data storage object is created, and an observable object is defined in the data storage object, wherein the data storage object is used for storing data in a data stream;
after the view is rendered for the first time, subscribing the observable object in a componentDIdMount method of the PureComponent component life cycle by the current view;
when receiving the updated data, acquiring the current data in the data storage object, merging the updated data and the current data, and calling the field of the observable object multicast with data change;
and when the field with the data change is the same as the initial field of the view, calling a forced updating method to refresh the current view.
Further, the creating a data storage object and defining an observable object in the data storage object further comprises:
and defining a data registration method and a data acquisition method in the data storage object.
Further, the primary rendering of the view specifically includes:
initializing the view, injecting a unique mapping field corresponding to the view into a constructor of the view, and injecting initialization data for the view.
Further, when the view component is destroyed, the subscription of the observable object is cancelled.
Further, the receiving the update data further includes: page level interface data is intercepted.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art would appreciate that the modules, elements, and/or method steps of the various embodiments described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.

Claims (10)

1.一种数据流管理框架,其特征在于,包括:1. a data flow management framework, is characterized in that, comprises: 存储组件:用于提供一个单例模式的数据存储对象和一个可观察对象,所述数据存储对象用于存储数据流中数据,所述可观察对象用于控制视图的刷新Storage component: used to provide a singleton mode data storage object and an observable object, the data storage object is used to store data in the data stream, and the observable object is used to control the refresh of the view 视图组件:用于在PureComponent组件生命周期的componentDIdMount方法中订阅所述可观察对象,当可观察对象多播发生数据变更的字段与初始字段相同时,调用强制更新方法刷新视图;所述初始字段为视图初次渲染时,为渲染视图绑定的唯一映射字段;View component: It is used to subscribe the observable object in the componentDIdMount method of the PureComponent component life cycle. When the field of the data change of the observable object multicast is the same as the initial field, the forced update method is called to refresh the view; the initial field is When the view is first rendered, the unique mapping field bound to the rendered view; 控制组件:用于接收传入的更新数据,并获取所述数据存储对象中的当前数据,合并所述更新数据和当前数据后,调用所述可观察对象多播发生数据变更的字段;Control component: used to receive the incoming update data, and obtain the current data in the data storage object, and after merging the update data and the current data, call the observable object to multicast the field of the data change; 服务组件:用于定义请求服务端的接口数据,将请求获得的数据进行请求逻辑与业务逻辑分离。Service component: used to define the interface data of the request server, and separate the request logic from the business logic of the data obtained by the request. 2.根据权利要求1所述的框架,其特征在于,所述存储组件还包括:2. The frame of claim 1, wherein the storage assembly further comprises: 在所述存储组件中定义数据注册方法和数据获取方法。A data registration method and a data acquisition method are defined in the storage component. 3.根据权利要求1所述的框架,其特征在于,所述视图组件还包括:3. The framework of claim 1, wherein the view component further comprises: 初始化所述视图组件,向所述视图组件的构造器中注入视图对应的控制组件中的唯一映射字段,并注入控制组件的初始化数据。Initialize the view component, inject the unique mapping field in the control component corresponding to the view into the constructor of the view component, and inject the initialization data of the control component. 4.根据权利要求1所述的框架,其特征在于,所述视图组件还包括:4. The framework of claim 1, wherein the view component further comprises: 当所述视图组件销毁时,取消所述可观察对象的订阅。Unsubscribe from the observable when the view component is destroyed. 5.根据权利要求1所述的框架,其特征在于,所述服务组件还包括:5. The framework of claim 1, wherein the service component further comprises: 拦截页面级接口数据。Intercept page-level interface data. 6.一种数据流管理方法,其特征在于,包括:6. A data flow management method, comprising: 单例模式下,创建一个数据存储对象,并在所述数据存储对象中定义一个可观察对象,其中,所述数据存储对象用于存储数据流中数据;In the singleton mode, a data storage object is created, and an observable object is defined in the data storage object, wherein the data storage object is used to store data in the data stream; 视图初次渲染完成后,当前视图在PureComponent组件生命周期的componentDIdMount方法中订阅所述可观察对象;After the initial rendering of the view is completed, the current view subscribes to the observable object in the componentDIdMount method of the PureComponent component life cycle; 当接收到更新数据后,获取所述数据存储对象中的当前数据,合并所述更新数据和当前数据后,调用所述可观察对象多播发生数据变更的字段;After receiving the update data, obtain the current data in the data storage object, and after merging the update data and the current data, call the observable object to multicast the field of the data change; 当所述发生数据变更的字段与视图初始字段相同时,调用强制更新方法刷新当前视图;所述初始字段为视图初次渲染时,为渲染视图绑定的唯一映射字段;When the field in which the data is changed is the same as the initial field of the view, the forced update method is invoked to refresh the current view; the initial field is the unique mapping field bound to the rendering view when the view is rendered for the first time; 定义请求服务端的接口数据,将请求获得的数据进行请求逻辑与业务逻辑分离。Define the interface data of the request server, and separate the request logic from the business logic for the data obtained by the request. 7.根据权利要求6所述的方法,其特征在于,所述创建一个数据存储对象,并在所述数据存储对象定义一个可观察对象还包括:7. method according to claim 6 is characterized in that, described creating a data storage object, and defining an observable object in described data storage object also comprises: 在所述数据存储对象中定义数据注册方法和数据获取方法。A data registration method and a data acquisition method are defined in the data storage object. 8.根据权利要求6所述的方法,其特征在于,所述视图初次渲染具体为:8. The method according to claim 6, wherein the initial rendering of the view is specifically: 初始化所述视图,向所述视图的构造器中注入视图对应的唯一映射字段,并为所述视图注入初始化数据。Initialize the view, inject the unique map field corresponding to the view into the constructor of the view, and inject initialization data for the view. 9.一种终端设备,包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机程序,其特征在于,所述处理器执行所述计算机程序时实现如权利要求1至5中任一项所述数据流管理的框架。9. A terminal device, comprising a memory, a processor and a computer program stored in the memory and running on the processor, wherein the processor implements the computer program as claimed in the claims when executing the computer program The framework for data flow management described in any one of 1 to 5. 10.一种计算机可读存储介质,所述计算机可读存储介质存储有计算机程序,其特征在于,所述计算机程序被处理器执行时实现如权利要求1至5中任一项所述数据流管理的框架。10. A computer-readable storage medium storing a computer program, characterized in that, when the computer program is executed by a processor, the data flow according to any one of claims 1 to 5 is implemented management framework.
CN201810796198.7A 2018-07-19 2018-07-19 Data stream management framework, method, terminal equipment and storage medium Active CN109032587B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810796198.7A CN109032587B (en) 2018-07-19 2018-07-19 Data stream management framework, method, terminal equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810796198.7A CN109032587B (en) 2018-07-19 2018-07-19 Data stream management framework, method, terminal equipment and storage medium

Publications (2)

Publication Number Publication Date
CN109032587A CN109032587A (en) 2018-12-18
CN109032587B true CN109032587B (en) 2021-11-26

Family

ID=64643256

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810796198.7A Active CN109032587B (en) 2018-07-19 2018-07-19 Data stream management framework, method, terminal equipment and storage medium

Country Status (1)

Country Link
CN (1) CN109032587B (en)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111258670B (en) * 2020-01-08 2023-09-22 北京字节跳动网络技术有限公司 Method and device for managing component data, electronic equipment and storage medium
CN112241282B (en) * 2020-10-27 2024-02-23 上海万向区块链股份公司 Global state data management method and system based on reaction project
CN112579237B (en) * 2020-12-17 2024-06-11 百果园技术(新加坡)有限公司 Event response method, device, equipment and medium based on MVVM mode
CN113434176A (en) * 2021-06-29 2021-09-24 青岛海尔科技有限公司 Data updating processing method and device, storage medium and electronic device
CN114924759B (en) * 2022-03-31 2025-02-11 北京达佳互联信息技术有限公司 Information updating method, device, electronic device and storage medium
CN114924722B (en) * 2022-04-27 2025-04-29 平安国际智慧城市科技股份有限公司 Bidirectional binding method, device, equipment and storage medium for form data
CN116610319B (en) * 2023-06-06 2024-05-14 易智瑞信息技术有限公司 A method and system for building map applications based on a low-code platform
CN118861106B (en) * 2024-09-29 2024-11-22 中电安世(成都)科技有限公司 A data flow analysis and processing method, system and storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106484412A (en) * 2016-09-30 2017-03-08 浙江大学 A kind of two-way binding implementation method of the front end data based on accessor abduction
EP3161683A1 (en) * 2014-06-25 2017-05-03 Microsoft Technology Licensing, LLC Stream-based reactive programming platform
CN107291523A (en) * 2017-08-01 2017-10-24 北京亚鸿世纪科技发展有限公司 A kind of web front end message bus system
CN107301048A (en) * 2017-06-23 2017-10-27 北京中泰合信管理顾问有限公司 Using the internal control and management system of response type sharing application framework

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8464281B2 (en) * 2010-08-18 2013-06-11 Sas Institute, Inc. Techniques to remotely access object events

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3161683A1 (en) * 2014-06-25 2017-05-03 Microsoft Technology Licensing, LLC Stream-based reactive programming platform
CN106484412A (en) * 2016-09-30 2017-03-08 浙江大学 A kind of two-way binding implementation method of the front end data based on accessor abduction
CN107301048A (en) * 2017-06-23 2017-10-27 北京中泰合信管理顾问有限公司 Using the internal control and management system of response type sharing application framework
CN107291523A (en) * 2017-08-01 2017-10-24 北京亚鸿世纪科技发展有限公司 A kind of web front end message bus system

Also Published As

Publication number Publication date
CN109032587A (en) 2018-12-18

Similar Documents

Publication Publication Date Title
CN109032587B (en) Data stream management framework, method, terminal equipment and storage medium
CN107291456B (en) Multi-screen display control method and system
CN108432200B (en) Method for protecting and controlling access to private personal information
CN107133309B (en) Method and device for storing and querying process example, storage medium and electronic equipment
CN111090691B (en) Data processing method and device, electronic equipment and storage medium
WO2007047900A2 (en) System and method for displaying data on a thin client
US9350738B2 (en) Template representation of security resources
CN110300328A (en) A kind of video playing control method, device and readable storage medium storing program for executing
US20220407795A1 (en) Centralized, scalable, resource monitoring system
EP3813326B1 (en) Method and apparatus for processing webpage, device, and storage medium
CN107396199A (en) Barrage method for exhibiting data and device, computer-readable recording medium
CN110321120B (en) Data processing method, data processing apparatus, and computer-readable storage medium
US11831735B2 (en) Method and device for processing mini program data
CN108933947B (en) Bullet screen display method and device
CN110008261B (en) External change detection
US20170188214A1 (en) Method and electronic device for sharing multimedia information
US10341420B1 (en) Approaches for preparing and delivering bulk data to clients
CN111177558B (en) Channel service construction method and device
US20170169792A1 (en) Electronic device and method for releasing content to multiple terminals
CN115809056B (en) Component multiplexing implementation method and device, terminal equipment and readable storage medium
CN110083323A (en) A kind of method and device for realizing mostly display and multi-user concurrent
WO2018205390A1 (en) Control layout display control method, system, and apparatus, and computer readable storage medium
Chen et al. MSA: A Novel App Development Framework for Transparent Multiscreen Support on Android Apps
CN107066180A (en) A kind of task creating method and its system based on VR operations
CN114675898A (en) Page jump method, computer device and computer readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20250423

Address after: Building 7, No. 99 Xiangyun North Road, High tech Zone, Ningbo City, Zhejiang Province 315000, China

Patentee after: Ningbo Jingda Technology Co.,Ltd.

Country or region after: China

Address before: 430000 East Lake Development Zone, Wuhan City, Hubei Province, No. 1 Software Park East Road 4.1 Phase B1 Building 11 Building

Patentee before: WUHAN DOUYU NETWORK TECHNOLOGY Co.,Ltd.

Country or region before: China