CN109656536B - Push module modularization method and client - Google Patents
Push module modularization method and client Download PDFInfo
- Publication number
- CN109656536B CN109656536B CN201811592426.5A CN201811592426A CN109656536B CN 109656536 B CN109656536 B CN 109656536B CN 201811592426 A CN201811592426 A CN 201811592426A CN 109656536 B CN109656536 B CN 109656536B
- Authority
- CN
- China
- Prior art keywords
- push
- module
- client
- logic
- component
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the application discloses a push module componentization method, which is used for enabling the obtained push components to realize decoupling among business components with clear architectures at a client side, and enabling the business components to be closed in units of business during a promotion peak period so as to ensure the smooth execution of core business components. The method in the embodiment of the application comprises the following steps: the client establishes a push module; the client side obtains relevant codes of push logic, wherein the relevant codes of the push logic comprise codes corresponding to push logics of different service functions in the first application; the client encapsulates the relevant codes of the push logic in the push module to obtain a push component; the client receives a push message sent by a server; and the client analyzes the push message through the push component and displays the processed push message.
Description
Technical Field
The present application relates to the field of client development, and in particular, to a push module componentization method and a client.
Background
With the continuous iteration of Application (APP) versions and the continuous increase of new functions, services become more and more complex, the number of APP service modules may also continue to increase, and the code of each service module becomes more and more. The development efficiency of the APP architecture under a single project is inevitably influenced, the maintenance cost of the project is increased, each engineer needs to be familiar with the codes, multi-person collaborative development is difficult to perform, a computer is extremely blocked when the Android project compiles the codes, the codes under the single project are seriously coupled, and recompilation and packaging tests are required after each code is modified, so that time is consumed, and most importantly, the codes are required to be subjected to unit tests.
Disclosure of Invention
The embodiment of the application provides a method for modularizing a push module and a client, the push module is used for enabling the clear service modules of the client to be coupled, each service module can complete independent APP release according to BU requirements, developers are easy to develop, the speed of function development and debugging is increased in development, the service modules are deleted integrally, added and replaced easily, and redundant files such as code resources in engineering are reduced.
In view of this, a first aspect of the present embodiment provides a push module componentization method, which may include:
the client establishes a push module;
the client side obtains relevant codes of push logic, wherein the relevant codes of the push logic comprise codes corresponding to push logics of different service functions in the first application;
the client encapsulates the relevant codes of the push logic in the push module to obtain a push component;
the client receives a push message sent by a server;
and the client analyzes the push message through the push component and displays the processed push message.
Alternatively, in some embodiments of the present application,
the client obtains a push component according to the relevant code of the push logic and the push module, and the push component comprises:
and the client decouples and extracts the push module, and adds the relevant codes of the push logic to obtain the push component.
Optionally, in some embodiments of the present application, the receiving, by the client, a push message sent by a server includes:
and the client receives the push message sent by the server through the push component.
Optionally, in some embodiments of the present application, the push message includes a user interface push message and a silent push message.
Optionally, in some embodiments of the present application, the push message includes a remote push message and a local push message.
Optionally, in some embodiments of the present application, the creating, by the client, a push module includes:
the client responds to the operation of a user and generates a creation instruction;
and the client executes the creating instruction to create the pushing module.
Optionally, in some embodiments of the present application, the creating, by the client, a push module includes:
the client receives a creation instruction sent by a server;
and the client executes the creating instruction to create the pushing module.
A second aspect of an embodiment of the present application provides a client, which may include:
the creating module is used for creating a pushing module;
the system comprises an acquisition module, a processing module and a display module, wherein the acquisition module is used for acquiring relevant codes of push logic, and the relevant codes of the push logic comprise codes corresponding to push logic of different service functions in first application;
an obtaining module, configured to encapsulate the relevant code of the push logic in the push module to obtain a push component;
the receiving module is used for receiving the push message sent by the server;
and the display module is used for displaying the push message through the push component.
Alternatively, in some embodiments of the present application,
the obtaining module is specifically configured to decouple and extract the pushing module, and add the relevant codes of the pushing logic to obtain the pushing component.
Alternatively, in some embodiments of the present application,
and the receiving module is specifically used for receiving the push message sent by the server through the push component.
Optionally, in some embodiments of the present application, the push message includes a user interface push message and a silent push message.
Optionally, in some embodiments of the present application, the push message includes a remote push message and a local push message.
Alternatively, in some embodiments of the present application,
the creating module is specifically used for responding to the operation of a user and generating a creating instruction; and executing the creating instruction to create the pushing module.
Alternatively, in some embodiments of the present application,
the creating module is specifically used for receiving a creating instruction sent by the server; and executing the creating instruction to create the pushing module.
In a third aspect, an embodiment of the present invention provides a client, including a memory and a processor, where the processor is configured to implement, when executing a computer program stored in the memory, the steps of the push module componentization method described in the foregoing first aspect embodiment.
In a fourth aspect, an embodiment of the present invention provides a readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the push module componentization method described in the foregoing first aspect embodiment.
According to the technical scheme, the embodiment of the application has the following advantages:
in the embodiment of the application, a client establishes a push module; the client side obtains relevant codes of push logic, wherein the relevant codes of the push logic comprise codes corresponding to push logics of different service functions in the first application; the client encapsulates the relevant codes of the push logic in the push module to obtain a push component; the client receives a push message sent by a server; and the client analyzes the push message through the push component and displays the processed push message. The obtained pushing assembly can enable the framework of the client to be clear, the service assemblies are coupled, each service assembly can complete independent APP release according to requirements, developers can feel easier in development, the speed of function development and debugging is increased in development, the service assemblies are easy to delete, add and replace integrally, and redundant files such as code resources in engineering are reduced.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the embodiments and the drawings used in the description of the prior art, and obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained according to the drawings.
FIG. 1 is a diagram of a system architecture to which embodiments of the present application are applied;
FIG. 2 is a diagram of an embodiment of a method for push module componentization in an embodiment of the present application;
FIG. 3 is a diagram illustrating an embodiment of a method for processing a push message according to an embodiment of the present application;
FIG. 4 is a schematic diagram of an embodiment of a client in an embodiment of the present application;
FIG. 5A is a schematic diagram of an embodiment of a client in an embodiment of the present application;
FIG. 5B is a schematic diagram of another embodiment of the client in the embodiment of the present application;
FIG. 5C is a schematic diagram of another embodiment of the client in the embodiment of the present application;
FIG. 6 is a schematic diagram of another embodiment of a client in the embodiment of the present application;
fig. 7 is a schematic diagram of an embodiment of a computer-readable storage medium according to an embodiment of the present invention.
Detailed Description
The embodiment of the application provides a method for modularizing a push module and a client, the push module can be used for enabling the architecture of the client to be clear, the connection and the coupling among service components can be completed, each service component can complete independent APP release according to BU requirements, developers can feel easier in development, the speed of function development and debugging is increased in development, the service components can be deleted, added and replaced easily in the whole process, and redundant files such as code resources in engineering are reduced; and service degradation, wherein the service component can be closed in service unit during the promotion peak period, and the smooth execution of the core service component is ensured.
For a person skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some embodiments of the present application, and not all embodiments. The embodiments in the present application shall fall within the protection scope of the present application.
Nowadays, the market of mobile APP is full of flowers, and many large-scale companies and huge companies are developed through APP entrepreneurship; the APP is richer in types, has electronic commerce, has videos, has social contact, has tools and the like, basically covers each corner of each business, is not only functionally inventive for having competitive APP, but also has more diversified and fuller contents, and therefore has huge engineering. If all codes of a good architecture are not strongly coupled together and functions are directly dependent, a plurality of problems occur; for example:
1. the function of the patient is difficult to modify, and the patient can pull the whole body. In many places, if the API (Application Programming Interface) writes poorly and the package is not well, calls that require many places to be changed to one place will occur.
2. The removal of redundancy is complicated by the excessive redundant obsolete code resources in the update iteration work and many bugs are likely to occur.
Fig. 1 is a block diagram of a system architecture to which embodiments of the present application are applied. In fig. 1, the method may include:
DY Push Notification Service: and providing a push API (application program interface) externally, including initialization, push configuration, push receiving and the like, and calling corresponding internal modules for processing.
Getui SDK: the pushed SDK may be later conveniently replaced with other third party SDKs.
DY Notification Handler Center: the carrier of the DY Notification Handler comprises a plurality of examples realizing the DY Push Notification Handler Protocol and is responsible for distributing Push messages to each Handler.
DY Push Notification Handler Protocol: the protocol of the message handling object is abstracted.
DY Notification Handler: and the system is used for processing the object of the specific service logic of the message and realizing respective service logic after analyzing the message.
DY Notification Tag Manager: and the system is responsible for managing the class of the added, deleted and modified push labels.
A brief description of the terms referred to in this application may be given first. As follows:
the components are generally related to exhibition, visual change and interaction optimization are the easiest iteration of a product, so most of the framework cores related to the components are all the implementation of a View layer, for example, Vue and reach regard themselves as just "View", although exhibition and interaction are continuously changed, data displayed at the bottom layer are not changed very often, View is an appearance, and data is fundamental, so how to better display the data to the View is also considered by each component, concepts such as unidirectional data binding and bidirectional data binding are derived, and communication between the components is also data as a bridge.
Many repetitive functions, such as pop-up layer prompt boxes, are generated in each page of a project, and such as a pure non-business User Interface (UI) becomes a UI component in a general sense, and an original front-end component is referred to as a UI component only.
The component development is divided into two modes, one is a development test mode, and the other is a release mode:
1. developing a test pattern: the mode is characterized in that the lower component of the mode is an independent module mode, the module can operate independently, and the test can be developed independently as long as the mode is ensured not to depend on other services.
2. And (3) release mode: at this time, the components are combined by the main project dependence according to the library mode, release operation is carried out, and all services are combined into a complete app release operation.
The technical solution of the present application is further described below by way of an embodiment, and as shown in fig. 2, a schematic diagram of an embodiment of a method for modularizing a push module in the embodiment of the present application is shown, where the method may include:
201. the client creates a push module.
Illustratively, the client may include a general handheld electronic terminal such as a smart phone, a portable terminal, a Personal Digital Assistant (PDA), a Portable Multimedia Player (PMP) device, a notebook (Note Pad), a Wireless Broadband (Wibro) terminal, a tablet (PC), and a smart PC.
The client creates a push module, which may include but is not limited to the following implementation:
(1) the client responds to the operation of a user and generates a creation instruction; and the client executes the creating instruction to create the pushing module.
(2) The client receives a creation instruction sent by a server; and the client executes the creating instruction to create the pushing module.
1. Main engineering (shell engineering module): the main responsibility is not to fill any specific business logic, and is mainly used for operations such as using combined business components, initializing configuration, issuing application configuration and the like.
2. Module/library: specific business logic is mainly realized, and business independence is guaranteed as much as possible, for example, almost every bu function block of a large-scale app like the existing hand panning can be taken out to be used as an independent business app. But without this large it is also possible to distinguish components according to a smaller business logic, for example: shopping cart components, cash register desk components, user center components, etc., and more particularly, to their own item needs.
3. Public library (library): the tool class used in public, sdk and other libraries, such as eventbus, xutils, rxandroid, custom tool class and the like, can be made into a common commonsdk, and can also realize the extraction and the fine use according to the requirement.
The relationship between them is that the main project depends on the component and the component depends on the public library.
202. The client side obtains relevant codes of push logic, wherein the relevant codes of the push logic comprise codes corresponding to push logics of different service functions in the first application.
Illustratively, the first application may be a fish fighting application, and the push logic of the different business functions may include a code corresponding to a push logic of an advertisement class, a code corresponding to a push logic of a video class, and the like.
203. And the client encapsulates the relevant codes of the push logic in the push module to obtain a push component.
The obtaining, by the client, a push component according to the relevant code of the push logic and the push module may include: and the client decouples and extracts the push module, and adds the relevant codes of the push logic to obtain the push component.
Decoupling and abstraction are common concepts in software development, with the aim of contacting the direct dependencies of two classes, usually by adding intermediate layers or using abstract interfaces. For example, there are two classes, one class is named as a and the other class is named as B, there is a function method called as scratch in the class a, a parameter needs to be transmitted, and the type is B. Thus, the class A must know the specifics of the class B, i.e., class A depends directly on class B. The decoupling is done by changing the parameters entered by grabbing the method to an abstract type, food. Thus, A does not need to directly depend on class B. Another way is to use intermediate layer bridging, where both classes depend on the other, so that they can be separated and do not depend directly on each other.
The decoupling pull-away scheme for pushing the edge is that when a push is received before and a live broadcast room needs to be jumped, the push component needs to know the object of the live broadcast room, namely, the push component directly depends on the object. After the decoupling, the push module is only responsible for receiving push and analysis, and after the message analysis is completed, the push module is used for inquiring each message executor (a plurality of message executors which are responsible for different services, such as live broadcast, webpage and the like) in the push center, and then the message is concerned. At the moment, the live broadcast executor is inquired to care about the message, the message is transmitted to the executor, the following jump live broadcast room is taken charge of by other parties, and the push module can not know that the live broadcast room exists.
Illustratively, the encapsulating, by the client, the relevant code of the push logic in the push module to obtain the push component may include:
(1) extracting Appendegate push codes into the component, and decoupling;
(2) moving the push SDK into the component, and configuring logic;
(3) the method comprises the following steps of (1) taking out, decoupling and reconstructing a DY Remote Notification Manager code (which can comprise layered design building, local push logic taking out, Remote push logic taking out and Remote push logic taking out);
(4) moving individual push tag management logic from the personal hub to the inside of the push component (logic migration, old code deletion, personal hub, applegerate redundancy dependency deletion);
(5) writing a main project forwarding code, and solving the problem of logic processing (skip logic forwarding and local push state logic forwarding) needing to be forwarded to a main project;
(6) push Handler configuration (Handler configuration File Plist writing, configuration file parsing, Handler registration logic).
The following is a detailed description of the above steps, as follows:
1. the original push receiving logic is directly written in an Apdelegate file and comprises push registration, deviceToken registration, individual push SDK initialization and specific implementation of a push proxy callback method.
The specific implementation of the logic is extracted into the pushing component, so that the inside of Apdelegat is as simple as possible, the responsibility is single, and the coupling degree is reduced. The AppDelegate only needs to call various interfaces provided by the pushing module.
2. The push SDK is used as a bottom layer service SDK, and originally directly depended on by AppDelegate, the whole SDK is moved and packaged into the push component, and is packaged by an SDKManager, the external part calls an interface provided by the SDKManager, the SDKManager calls the interface of the push SDK, and the external caller is isolated from the push SDK.
And in the later stage, if the pushing SDK of other manufacturers needs to be replaced, only the internal implementation of the SDKManager needs to be modified, the outside is not affected, and the logic of extraction comprises the initialization of the pushing SDK, the registration of devicetoken, the tag operation and the like.
3. Original analysis of the push message and the whole message processing logic are placed in a RemoteNotification manager, so that the push message is overstaffed, the coupling is serious, the single responsibility in a design mode is violated, and the push message is split into 3 modules: 1. a message receiving module ((PushNotificationService)); 2. a message Handler center (Handler center, responsible for storing various handlers for pushnotifiationservice query); 3. a message handling module (handler, responsible for handling specific message events).
4. And configuring the defined Handler into a plist file, reading and analyzing the plist file by the push component when the app is started, creating various handlers according to the configuration, and adding the handlers into the Handler center.
5. When receiving the push message, the pushNotification service now analyzes the message, then inquires the Handler center which Handler wants to process the message, the Handler center traverses all the handlers thereof and calls the interfaces thereof, when the Handler returns that the result is that the Handler wants to process the message, the pushNotification service transmits the message to the Handler, and the Handler processes the specific service of the message.
Optionally, after the push component is obtained, operations such as testing, bug modification, component tag marking, review problem solving, code merging and the like can also be performed.
The noun meaning in the componentized engineering model is as follows:
an integration mode: all the service components are depended on by the APP shell engineering to form a complete APP;
component mode: service components can be independently developed, and each service component is an APP;
APP shell engineering: the system is responsible for managing each service component and packaging apk without specific service function;
and (4) service components: independently forming a project according to specific business of a company;
functional components: providing some basic functions for developing the APP, such as print logs, treemaps, etc.;
a Main component: the method comprises the steps that the method belongs to a service component, and an APP starting page and a main interface are designated;
a Common component: the function module is a basis for supporting the service module and providing functions required by most service modules, such as providing network request functions.
204. And the client receives the push message sent by the server.
The client receives the push message sent by the server, and may include: and the client receives the push message sent by the server through the push component.
Illustratively, the push messages may include user interface push messages and silent push messages. Alternatively, the push messages may include remote push messages and local push messages. Alternatively, the push message may comprise an advertising type push message, a live broadcast push message, or the like.
205. And the client analyzes the push message through the push component and displays the processed push message.
After receiving the push message sent by the server, the client can analyze the push message through the push component and display the processed push message.
Exemplary ways in which the client displays the push message include, but are not limited to: displaying the processed push message in a floating manner, or displaying the processed push message in a shaking manner, or displaying the processed push message in a gradual change manner, or displaying the processed push message in an amplifying manner and then in a reducing manner.
In the embodiment of the application, a client establishes a push module; the client side obtains relevant codes of push logic, wherein the relevant codes of the push logic comprise codes corresponding to push logics of different service functions in the first application; the client encapsulates the relevant codes of the push logic in the push module to obtain a push component; the client receives a push message sent by a server; and the client analyzes the push message through the push component and displays the processed push message. The obtained pushing assembly can enable the framework of the client to be clear, the service assemblies are coupled, each service assembly can complete independent APP release according to requirements, developers can feel easier in development, the speed of function development and debugging is increased in development, the service assemblies are easy to delete, add and replace integrally, and redundant files such as code resources in engineering are reduced; further, the service is degraded, the service component can be closed in service unit during the promotion peak period, and the smooth execution of the core service component is ensured.
As shown in fig. 3, a schematic diagram of an embodiment of a method for processing a push message in an embodiment of the present application may include:
301. the client acquires push messages, wherein the push messages comprise push messages with different service functions.
Illustratively, the push messages may include user interface push messages and silent push messages. Alternatively, the push messages may include remote push messages and local push messages. Alternatively, the push message may comprise an advertising type push message, a live broadcast push message, or the like.
302. And the client processes the push message in the push component to correspondingly obtain different processed messages, and codes corresponding to push logics of different service functions in the first application are packaged in the push component.
The processing of the push message by the client to obtain different processing messages correspondingly may include: and the client analyzes the push message to obtain different processing messages correspondingly.
303. And the client displays the different processing messages through the push component.
The client displays the different processing messages through a push component, including but not limited to the following implementation modes:
(1) and the client displays the different processing messages in a rotating mode through the pushing component. Alternatively, the first and second electrodes may be,
(2) and the client displays the different processing messages in an amplifying mode through the push component. Alternatively, the first and second electrodes may be,
(3) and the client displays the unused processing messages in a gradient mode through the pushing component.
In the embodiment of the application, a client acquires push messages, wherein the push messages comprise push messages with different service functions; the client processes the push message in a push component to correspondingly obtain different processed messages, and codes corresponding to push logics of different service functions in the first application are packaged in the push component; and the client displays the different processing messages through the push component. The client uses the pushing component to process the pushing message, different processing messages are correspondingly obtained, and then the different processing messages are displayed through the pushing component, so that system resources are saved.
Optionally, in some embodiments of the present application, the method may further include:
the client side obtains a deleting instruction;
and the client deletes the first target push message according to the deletion instruction, wherein the push message comprises the first target push message.
Optionally, in some embodiments of the present application, the method may further include:
the client side obtains an adding instruction;
and the client adds a second target push message according to the adding instruction, wherein the push message comprises the second target push message.
In the embodiment of the application, each pushing SDK is packaged in the pushing assembly and is not exposed outside, the pushing assembly provides interface access to the outside, and the externally exposed interfaces of the pushing assembly can be kept unchanged as much as possible when the SDK is replaced subsequently; packaging pushing related logic in Apdelegat into a pushing component, wherein the Apdelegat does not bear excessive logic processing and is only responsible for calling an interface provided by the component; moving the tag adding, deleting and modifying operation from the personal central component to the interior of the pushing component, and setting a module for special maintenance; analyzing and processing the push message by different service modules, and separating the push message into different analyzers and processing types for processing, wherein the analyzers and the processing types are independent from each other; and if the pushing component is subsequently multiplexed into other APPs, customizing the parser according to the service scene.
For example, when testing the push component, the items tested may include, but are not limited to, the following descriptions:
1. the testing of the remote push message may include:
(1) jump direct broadcasting room (type 1, 9)
For example: broadcast reminding, horizontal screen, vertical screen and audio.
(2) Jump video (type 2, 6)
For example: horizontal screen, vertical screen, and fine selection set.
(3) Jump H5(type 3, 6)
For example: normal H5, birthday reminder.
(4) Old station mail edition (type 4)
(5) Fish bar (type 7, 11, 12)
For example: fish bar dynamics (type of announcement banner), fleet of vehicles, planet.
(6) Radio station (type as 8)
(7)log(type＝10)
2. The testing of the local push message may include:
(traffic distribution) -skip live broadcasting room (type 2) -skip H5(type 1) -skip video (type 3, 6) -video detail page-video topic-skip not (type 4) -skip home page (other types)
3. Testing of other push messages may include:
for example: new station information message
4. Abnormal situation
In the continuous wheat of the color value live broadcasting room, a prompt required for remote push jumping is received;
receiving the push in the broadcasting state, and not displaying;
currently, a corresponding local push is received in the live room, video detail page, H5, home page;
waking up the advertisement not to be displayed by pushing hot start;
a state where push is not allowed (e.g., when a wolf kills a game), push is not shown;
the method comprises the following steps that (1) small windows (video and audio) of a live broadcast room are eliminated when landing popup windows exist;
when jumping to H5, if it is currently the landscape screen that needs to be turned (live room, video details, small video).
5. Other points of attention
For example: APNS propelling movement, individual pushes away and passes through, and the propelling movement is received to the proscenium, and the propelling movement is received to the backstage, receives the propelling movement when APP does not start, gets a point.
As shown in fig. 4, a schematic diagram of an embodiment of a client in the embodiment of the present application may include:
a creating module 401, configured to create a push module;
an obtaining module 402, configured to obtain relevant codes of a push logic, where the relevant codes of the push logic include codes corresponding to push logics of different service functions in a first application;
an obtaining module 403, configured to encapsulate the relevant code of the push logic in the push module, so as to obtain a push component;
a receiving module 404, configured to receive a push message sent by a server;
a display module 405, configured to display the push message through the push component.
Alternatively, in some embodiments of the present application,
an obtaining module 403, specifically configured to decouple and extract the pushing module, and add the relevant code of the pushing logic to obtain the pushing component.
Alternatively, in some embodiments of the present application,
a receiving module 404, specifically configured to receive, by the push component, a push message sent by the server.
Optionally, in some embodiments of the present application, the push message includes a user interface push message and a silent push message.
Optionally, in some embodiments of the present application, the push message includes a remote push message and a local push message.
Alternatively, in some embodiments of the present application,
a creating module 401, configured to generate a creating instruction in response to an operation of a user; and executing the creating instruction to create the pushing module.
Alternatively, in some embodiments of the present application,
a creating module 401, specifically configured to receive a creating instruction sent by a server; and executing the creating instruction to create the pushing module.
As shown in fig. 5A, a schematic diagram of an embodiment of a client in the embodiment of the present application may include:
an obtaining module 501, configured to obtain a push message, where the push message includes push messages with different service functions;
a processing module 502, configured to process the push message in the push component to obtain different processed messages correspondingly, and encapsulate codes corresponding to push logics of different service functions in the first application in the push component;
a display module 503, configured to display different processed messages through the push component.
Optionally, in some embodiments of the present application, as shown in fig. 5B, which is a schematic view of another embodiment of the client in the embodiments of the present application, the client may further include:
the obtaining module 501 is further configured to obtain a deletion instruction;
a deleting module 504, configured to delete the first target push message according to the deletion instruction, where the push message includes the first target push message.
Optionally, in some embodiments of the present application, as shown in fig. 5C, which is a schematic view of another embodiment of the client in the embodiments of the present application, the client may further include:
the obtaining module 501 is further configured to obtain an adding instruction;
an adding module 505, configured to add a second target push message according to the adding instruction, where the push message includes the second target push message.
Alternatively, in some embodiments of the present application,
the processing module 502 is specifically configured to perform parsing on the push message, so as to obtain different processing messages correspondingly.
Alternatively, in some embodiments of the present application,
the display module 503 is specifically configured to perform parsing on the push message, and obtain different processed messages correspondingly.
Alternatively, in some embodiments of the present application,
the display module 503 is specifically configured to display different processed messages in an enlarged manner through the push component.
Alternatively, in some embodiments of the present application,
the display module 503 is specifically configured to display the different processing messages in a gradient manner through the push component.
As shown in fig. 6, a schematic diagram of another embodiment of the client in the embodiment of the present application may include:
including a memory 610, a processor 620, and a computer program 611 stored on the memory 620 and operable on the processor 620.
In one implementation, the processor 620, when executing the computer program 611, may implement the following steps:
creating a push module;
acquiring related codes of push logic, wherein the related codes of the push logic comprise codes corresponding to push logics with different functions in first application;
packaging the relevant codes of the pushing logic in the pushing module to obtain a pushing assembly;
receiving a push message sent by a server;
and analyzing the push message through the push component, and displaying the processed push message.
Optionally, in some embodiments of the present application, the processor 620 may further implement the following steps when executing the computer program 611:
and decoupling and extracting the pushing module, and adding the relevant codes of the pushing logic to obtain the pushing component.
Optionally, in some embodiments of the present application, the processor 620 may further implement the following steps when executing the computer program 611:
and receiving the push message sent by the server through the push component.
Optionally, in some embodiments of the present application, the push message includes a user interface push message and a silent push message.
Optionally, in some embodiments of the present application, the push message includes a remote push message and a local push message.
Optionally, in some embodiments of the present application, the processor 620 may further implement the following steps when executing the computer program 611:
responding to the operation of a user and generating a creation instruction;
and executing the creating instruction to create the pushing module.
Optionally, in some embodiments of the present application, the processor 620 may further implement the following steps when executing the computer program 611:
receiving a creation instruction sent by a server;
and executing the creating instruction to create the pushing module.
In another implementation, the processor 620, when executing the computer program 611, may implement the following steps:
acquiring push messages, wherein the push messages comprise push messages with different service functions;
processing the push message in a push component to correspondingly obtain different processing messages, and encapsulating codes corresponding to push logics of different service functions in the first application in the push component;
displaying the different processed messages through the push component.
Optionally, in some embodiments of the present application, the processor 620 may further implement the following steps when executing the computer program 611:
acquiring a deleting instruction;
and deleting a first target push message according to the deletion instruction, wherein the push message comprises the first target push message.
Optionally, in some embodiments of the present application, the processor 620 may further implement the following steps when executing the computer program 611:
acquiring an adding instruction;
and adding a second target push message according to the adding instruction, wherein the push message comprises the second target push message.
Optionally, in some embodiments of the present application, the processor 620 may further implement the following steps when executing the computer program 611:
and analyzing the push message to correspondingly obtain different processing messages.
Optionally, in some embodiments of the present application, the processor 620 may further implement the following steps when executing the computer program 611:
displaying, by the push component, the different processed messages in a rotating manner.
Optionally, in some embodiments of the present application, the processor 620 may further implement the following steps when executing the computer program 611:
and displaying the different processing messages in an amplifying mode through the push component.
Optionally, in some embodiments of the present application, the processor 620 may further implement the following steps when executing the computer program 611:
displaying, by the push component, the unused treatment messages in a graduated manner.
Referring to fig. 7, fig. 7 is a schematic diagram illustrating an embodiment of a computer-readable storage medium according to the present invention.
As shown in fig. 7, the present embodiment provides a computer-readable storage medium on which a computer program 711 is stored.
In one implementation, the computer program 711, when executed by a processor, may implement the following steps:
creating a push module;
acquiring related codes of push logic, wherein the related codes of the push logic comprise codes corresponding to push logics with different functions in first application;
packaging the relevant codes of the pushing logic in the pushing module to obtain a pushing assembly;
receiving a push message sent by a server;
and analyzing the push message through the push component, and displaying the processed push message.
Optionally, in some embodiments of the present application, the computer program 711 when executed by the processor may further implement the following steps:
and decoupling and extracting the pushing module, and adding the relevant codes of the pushing logic to obtain the pushing component.
Optionally, in some embodiments of the present application, the computer program 711 when executed by the processor may further implement the following steps:
and receiving the push message sent by the server through the push component.
Optionally, in some embodiments of the present application, the push message includes a user interface push message and a silent push message.
Optionally, in some embodiments of the present application, the push message includes a remote push message and a local push message.
Optionally, in some embodiments of the present application, the computer program 711 when executed by the processor may further implement the following steps:
responding to the operation of a user and generating a creation instruction;
and executing the creating instruction to create the pushing module.
Optionally, in some embodiments of the present application, the computer program 711 when executed by the processor may further implement the following steps:
receiving a creation instruction sent by a server;
and executing the creating instruction to create the pushing module.
In another implementation, the computer program 711, when executed by a processor, may implement the following steps:
acquiring push messages, wherein the push messages comprise push messages with different service functions;
processing the push message in a push component to correspondingly obtain different processing messages, and encapsulating codes corresponding to push logics of different service functions in the first application in the push component;
displaying the different processed messages through the push component.
Optionally, in some embodiments of the present application, the computer program 711 when executed by the processor may further implement the following steps:
acquiring a deleting instruction;
and deleting a first target push message according to the deletion instruction, wherein the push message comprises the first target push message.
Optionally, in some embodiments of the present application, the computer program 711 when executed by the processor may further implement the following steps:
acquiring an adding instruction;
and adding a second target push message according to the adding instruction, wherein the push message comprises the second target push message.
Optionally, in some embodiments of the present application, the computer program 711 when executed by the processor may further implement the following steps:
and analyzing the push message to correspondingly obtain different processing messages.
Optionally, in some embodiments of the present application, the computer program 711 may further implement the following steps when being executed by the processor:
displaying, by the push component, the different processed messages in a rotating manner.
Optionally, in some embodiments of the present application, the computer program 711 when executed by the processor may further implement the following steps:
and displaying the different processing messages in an amplifying mode through the push component.
Optionally, in some embodiments of the present application, the computer program 711 when executed by the processor may further implement the following steps:
displaying, by the push component, the unused treatment messages in a graduated manner.
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 several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should 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 application.
Claims (9)
1. A method of push module componentization, comprising:
the client establishes a push module;
the client side obtains relevant codes of push logic, wherein the relevant codes of the push logic comprise codes corresponding to push logics of different service functions in the first application;
the client encapsulates the relevant codes of the push logic in the push module to obtain a push component; the method comprises the following steps: the client decouples and extracts the push module, and adds the relevant codes of the push logic to obtain the push component;
the client receives a push message sent by a server; the push messages comprise push messages with different service functions;
and the client analyzes the push message through the push component and displays the processed push message.
2. The method of claim 1, wherein the client receives a push message sent by a server, and the method comprises:
and the client receives the push message sent by the server through the push component.
3. The method of claim 2, wherein the push messages comprise user interface push messages and silent push messages.
4. The method of claim 2, wherein the push messages comprise remote push messages and local push messages.
5. The method of claim 1, wherein the client creates a push module comprising:
the client responds to the operation of a user and generates a creation instruction;
and the client executes the creating instruction to create the pushing module.
6. The method of claim 1, wherein the client creates a push module comprising:
the client receives a creation instruction sent by a server;
and the client executes the creating instruction to create the pushing module.
7. A client, comprising:
the creating module is used for creating a pushing module;
the system comprises an acquisition module, a processing module and a display module, wherein the acquisition module is used for acquiring relevant codes of push logic, and the relevant codes of the push logic comprise codes corresponding to push logic of different service functions in first application;
an obtaining module, configured to encapsulate the relevant code of the push logic in the push module to obtain a push component; the client decouples and extracts the push module, and adds the relevant codes of the push logic to obtain the push component;
the receiving module is used for receiving a push message sent by the server; the push message comprises push messages with different service functions;
and the display module is used for analyzing the push message through the push component and displaying the processed push message.
8. A client, characterized in that it comprises a processor for implementing the steps of the push module componentization method according to any one of claims 1-6 when executing a computer program stored in a memory.
9. A readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the push module componentization method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811592426.5A CN109656536B (en) | 2018-12-25 | 2018-12-25 | Push module modularization method and client |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811592426.5A CN109656536B (en) | 2018-12-25 | 2018-12-25 | Push module modularization method and client |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109656536A CN109656536A (en) | 2019-04-19 |
| CN109656536B true CN109656536B (en) | 2022-08-16 |
Family
ID=66116155
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811592426.5A Active CN109656536B (en) | 2018-12-25 | 2018-12-25 | Push module modularization method and client |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109656536B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111666097B (en) * | 2020-06-01 | 2023-03-31 | 北京思特奇信息技术股份有限公司 | Capability domination method and device based on service scene |
| CN113485680B (en) * | 2021-06-30 | 2022-10-11 | 重庆长安汽车股份有限公司 | APP (application) component control system and method based on vehicle-mounted system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105391785A (en) * | 2015-11-25 | 2016-03-09 | 广州华多网络科技有限公司 | Method for processing service message and server |
| CN107783849A (en) * | 2017-09-27 | 2018-03-09 | 武汉斗鱼网络科技有限公司 | Event-handling method and client |
| CN107995169A (en) * | 2017-11-21 | 2018-05-04 | 厦门点触科技股份有限公司 | A kind of mobile phone games skeleton system based on micro services framework |
| CN108255545A (en) * | 2016-12-28 | 2018-07-06 | 阿里巴巴集团控股有限公司 | The funcall method, apparatus of inter-module and component based architecture system |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP5091923B2 (en) * | 2009-07-06 | 2012-12-05 | 株式会社東芝 | Electronic device and communication control method |
| CN107391115B (en) * | 2017-06-28 | 2018-10-23 | 武汉斗鱼网络科技有限公司 | A kind of method, apparatus and computer equipment for realizing pop-up alternative events |
| CN107370824A (en) * | 2017-08-16 | 2017-11-21 | 扈传平 | Shared charger baby and shared charger baby information interacting method |
| CN107729061A (en) * | 2017-10-12 | 2018-02-23 | 武汉市灯塔互动文化传播有限公司 | The modularization construction method of engineering project under a kind of ios platform |
| CN107908403A (en) * | 2017-11-10 | 2018-04-13 | 北京搜狐新动力信息技术有限公司 | A kind of collocation method and system of the modularization of mobile terminal business module |
| CN108712320B (en) * | 2018-04-23 | 2021-02-05 | 天津字节跳动科技有限公司 | Message pushing method and device |
| CN108848142B (en) * | 2018-05-31 | 2022-05-31 | 康键信息技术（深圳）有限公司 | Message pushing method and device, computer equipment and storage medium |
-
2018
- 2018-12-25 CN CN201811592426.5A patent/CN109656536B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105391785A (en) * | 2015-11-25 | 2016-03-09 | 广州华多网络科技有限公司 | Method for processing service message and server |
| CN108255545A (en) * | 2016-12-28 | 2018-07-06 | 阿里巴巴集团控股有限公司 | The funcall method, apparatus of inter-module and component based architecture system |
| CN107783849A (en) * | 2017-09-27 | 2018-03-09 | 武汉斗鱼网络科技有限公司 | Event-handling method and client |
| CN107995169A (en) * | 2017-11-21 | 2018-05-04 | 厦门点触科技股份有限公司 | A kind of mobile phone games skeleton system based on micro services framework |
Non-Patent Citations (3)
| Title |
|---|
| Design of Cordova Based Message Push Module for Cross-Platform Smart Home Application;Fagui Liu 等;《2015 Fifth International Conference on Instrumentation and Measurement, Computer, Communication and Control (IMCCC)》;20150920;635-639 * |
| 基于MBaaS架构的移动后端服务框架的研究与实现;李楚畅;《中国优秀博硕士学位论文全文数据库(硕士)信息科技辑》;20180315(第03期);I138-604 * |
| 组件化二（消息推送）;火星局;《https://www.jianshu.com/p/c10ae1c01a6d?utm_campaign=maleskine&utm_content=note&utm_medium=seo_notes&utm_source=recommendation》;20181017;1-9 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109656536A (en) | 2019-04-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100462917C (en) | Data container for user interface content data | |
| CN106412015B (en) | A kind of data publication method, equipment and system | |
| CN106775751A (en) | A kind of web front-end frame system and framework method | |
| CN103324471A (en) | Dynamic modification method for applied launcher icon, message transmitting method and terminal | |
| CN111814089A (en) | Page rendering method and device, rendering server and storage medium | |
| CN110020356A (en) | A kind of code generating method of page module, apparatus and system | |
| CN109656536B (en) | Push module modularization method and client | |
| CN111068328A (en) | Game advertisement configuration table generation method, terminal device and medium | |
| CN111427576B (en) | Method, device, storage medium and terminal for configuring application program interface | |
| CN111324390A (en) | Device and method for realizing APP content configuration and real-time update | |
| CN112528207B (en) | Activity page generation method and device and electronic equipment | |
| US20100179982A1 (en) | Method for auditing the data of a computer application of a terminal | |
| CN110347445A (en) | SDK call method, device, server and storage medium | |
| US8612996B2 (en) | Technique for integrating a distributed object system component with a service oriented architecture application | |
| CN112817591A (en) | Front-end page construction method and device | |
| US20130059613A1 (en) | System and method for providing end to end interactive mobile applications using sms | |
| CN114579182A (en) | Applet cross-end application method, related device and computer storage medium | |
| CN113900650A (en) | Data processing method and device, electronic equipment and readable storage medium | |
| CN113434315A (en) | Interface management method and device, storage medium and electronic equipment | |
| CN110673827B (en) | Resource calling method and device based on android system and electronic equipment | |
| CN105610699B (en) | A kind of information processing method, first terminal and second terminal | |
| CN112241373A (en) | Automatic test method, test device, processor and test system | |
| CN102184105A (en) | Data processing method based on modularity and data center system | |
| CN100543700C (en) | The method of customizing extract operation information and device in a kind of software execute process | |
| CN113312104A (en) | Advertisement conversion method and system based on small program |
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 |