WO2019010928A1

WO2019010928A1 - Communication method and system among multiple fragments

Info

Publication number: WO2019010928A1
Application number: PCT/CN2017/120152
Authority: WO
Inventors: 张磊; 张文明; 陈少杰
Original assignee: 武汉斗鱼网络科技有限公司
Priority date: 2017-07-10
Filing date: 2017-12-29
Publication date: 2019-01-17
Also published as: CN107368311B; CN107368311A

Abstract

A communication method and system among multiple Fragments. The method comprises: configuring a message controller for all Fragments in an interface, and registering all the Fragments in the message controller, wherein all the registered Fragments are under an equal relationship (S1); and on the basis of a command interface defined for each Fragment and an interface function of the command interface, forwarding the message of a source Fragment to a target Fragment by the message controller (S2). By the method, message managers are configured for all Fragments in the interface, communication among different Fragments is realized by the approach of forwarding messages by the message controller, so that chaos caused by direct communication among the plurality of Fragments is avoided; furthermore, when the plurality of Fragments have a nesting relationship, the problem in the prior art of complex communication due to the layer-by-layer issuing of messages can be avoided.

Description

Communication method and system between multiple Fragment

cross reference

The present application is hereby incorporated by reference in its entirety in its entirety in its entirety in its entirety in the the the the the the the the the the the the the the

Technical field

The present invention relates to the field of communication technologies, and in particular, to a communication method and system between multiple Fragment.

Background technique

In the Android development process, interface-related programming is usually involved. Fragment is a fragment element in the entire interface, which can be understood as Fragment as part of the interface.

An interface can load one or more fragments. For example, the entire interface contains three tab elements. Each tab element is a page in the interface. Tab pages can be switched between each other. A tab page can be switched by a Fragment. In the development process, a Fragment can control the business logic of a page, and multiple Fragment can separate and separate the business logic of each page, which is convenient for later maintenance.

Communication between multiple Fragments is required. The traditional way is to directly communicate between Fragment, so if the number of Fragment is large, the communication between Fragments will be confusing. At the same time, if there are nested reference relationships between multiple Fragments, When the top-level Fragment sends a message to the lowest-level Fragment, it needs to be forwarded layer by layer through the Fragment of each level, and the communication speed is slow.

Summary of the invention

The present invention provides a communication method and system between multiple Fragment that overcomes the above problems or at least partially solves the above problems.

According to a first aspect of the present invention, a communication method between multiple Fragments is provided, including:

S1, configuring a message controller for all Fragment fragments in the interface, and registering all Fragments in the message controller, wherein all registered Fragments are in an equal relationship;

S2, based on the command interface defined for each Fragment and its interface function, the message controller forwards the message of the source Fragment to the destination Fragment.

The invention has the beneficial effects that: configuring a message manager for all the Fragment in the interface, and implementing a Fragment to send a message to another Fragment by means of the message controller to avoid confusion of direct communication between the multiple Fragments; When there is a nested relationship between the Fragments, since all the Fragments registered in the message controller in this embodiment are in a peer relationship, when the source Fragment sends a message to the destination Fragment having a nested relationship, it is directly controlled by the message. The device forwards to the destination Fragment without passing through the first-level Fragment, avoiding the complicated communication problem caused by the need to send messages layer by layer.

Based on the above technical solutions, the present invention can also be improved as follows.

Further, the step S2 further includes:

A command interface is defined for each Fragment, and an interface function is defined for the command interface, and the interface function includes at least a message command word and a message body parameter.

Further, the step S2 further includes:

For all Fragments registered to the message controller, maintain a collection of objects in the message controller that hold all registered Fragment objects.

Further, the step S2 further includes:

When the message controller receives the message sent by the source Fragment, the message is sent to the destination Fragment in a broadcast manner or in a peer-to-peer manner.

Further, the step S2 further includes:

When the message controller receives the message sent by the source fragment, the message is broadcast to the Fragment registered with the message controller;

The Fragment that receives the message determines whether the message needs to be processed according to the message command word in the message.

Further, the step S2 further includes:

The message controller traverses all the Fragment objects in the object collection in a round-robin manner;

Each time a Fragment object is extracted, an interface function in the Fragment object is called, and the message is delivered to an interface function of the Fragment object, and the interface function determines whether the message needs to be processed according to the message command word in the message. .

Further, the message further includes a destination Fragment identifier, and the step S2 further includes:

The message controller receives the message sent by the source Fragment, and forwards the message to the destination Fragment according to the destination Fragment identifier in the message.

According to a second aspect of the present invention, there is also provided a communication system between multiple Fragments, comprising:

a configuration module configured to configure a message controller for all the Fragments in the interface;

a registration module, configured to register all the Fragment in the message controller;

The forwarding module is configured to forward the message of the source Fragment to the destination Fragment by the message controller based on the command interface defined for each Fragment and its interface function.

According to a third aspect of the present invention, an apparatus for a communication method between multiple Fragments is provided, including a processor, a memory, and a bus;

The processor and the memory complete communication with each other through the bus;

The memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the various implementation methods described above.

According to a fourth aspect of the present invention, there is provided a non-transitory computer readable storage medium storing computer instructions that cause the computer to perform the various implementation methods described above.

DRAWINGS

1 is a flow chart of a communication method between multiple Fragments according to an embodiment of the present invention;

2 is a block diagram showing a communication system connection between multiple Fragments according to another embodiment of the present invention;

3 is a block diagram showing the overall connection of a communication system between multiple Fragments according to still another embodiment of the present invention;

4 is a block diagram showing the internal connection of a message controller according to still another embodiment of the present invention;

FIG. 5 is a block diagram of an electronic device connection according to an embodiment of the present invention.

Detailed ways

The specific embodiments of the present invention are further described in detail below with reference to the drawings and embodiments. The following examples are intended to illustrate the invention but are not intended to limit the scope of the invention.

Referring to FIG. 1, a communication method between multiple Fragment according to an embodiment of the present invention is provided, including: S1, configuring a message controller for all Fragment fragments in an interface, and registering all Fragments in the message controller; S2 Based on the command interface defined for each Fragment and its interface function, the message controller forwards the message of the source Fragment to the destination Fragment.

In the development process of Android, interface-related programming is usually involved. There are often multiple Fragments in an interface. Fragment can be understood as a fragment element, that is, an interface can contain multiple fragment elements. A Fragment can manage the business logic of a page. Multiple Fragments can separate and separate the business logic of each page. Communication is required between each Fragment. The traditional way is to directly communicate between Fragment, that is, the source Fragment directly sends a message to the destination Fragment. In this way of communication, if the number of Fragment is large, the communication between Fragment will be confusing; at the same time, if there is a nested reference relationship between multiple Fragments, when the top Fragment sends a message to the lowest Fragment, It needs to be forwarded layer by layer, and the communication speed is slow.

Therefore, in order to solve the above problem, the present embodiment provides a simple communication method between a plurality of Fragments. In the specific implementation process, in order to realize communication between multiple Fragment, a communication protocol for communication between multiple Fragment is designed, and subsequent Fragments follow this protocol to communicate, specifically designing between multiple Fragment The communication protocol is to define command interfaces and interface functions for each Fragment in the interface. At the same time, a message controller is configured for all the Fragments in the interface, wherein the message controller is used to control all the Fragments. In this embodiment, based on the command interface and interface function defined for each Fragment, the message controller mainly implements forwarding of messages between multiple Fragments.

In this embodiment, when a Fragment sends a message to another Fragment, for convenience of description, the Fragment that sends the message is called the source Fragment, and the Fragment that receives the message is called the destination Fragment. The source Fragment first sends a message to the message controller, and the message controller forwards the message to the destination Fragment. The destination Fragment needs to receive the message from the message controller and needs to register with the message controller. Only the Fragment registered in the message controller can receive the message forwarded by the message controller. In addition, in the process of communication between the source Fragment and the message controller and the message controller and the destination Fragment, communication is implemented based on the above communication protocol.

In this embodiment, all the Fragment configuration message managers in the interface are implemented by the message controller to implement a Fragment to send a message to another Fragment to avoid confusion of direct communication between multiple Fragments; and when between multiple Fragments When there is a nested relationship, since all the Fragments registered in the message controller in this embodiment are in a peer relationship, when the source Fragment sends a message to the destination Fragment having a nested relationship, the message controller directly forwards the message to the destination. Fragment, without the need to pass the first-level Fragment, avoids the complicated communication problems that need to be sent layer by layer.

On the basis of the foregoing embodiment, in an embodiment of the present invention, the step S2 further includes: defining a command interface for each Fragment, and defining an interface function for the command interface, where the interface function includes at least a message command word. And message body parameters.

In the process of designing a communication protocol between multiple Fragments, a set of command interfaces is designed for each Fragment. In order to be compatible with all messages, the designed communication protocol can be divided into two parts. The first part is the message command word, which is mainly used. To indicate the type of message, the second part is the message body, which is the specific content of the message. The program code of the designed command interface is as follows:

Interface indicates that the protocol is an interface protocol, IMessage indicates the name of the interface protocol; onMessage indicates the interface function contained in the interface protocol, and its return value is of type void, that is, there is no return value. The interface function contains two parameter information, one is a String (string) type command, command indicates the message command word issued, and the other parameter is the Object type message. The reason is designed as Object type to be able to All types of messages are received through this interface function.

By observing, it can be found that each parameter in the above interface function has a prefix @NoNullable, indicating that the parameter passed to the interface function cannot be null (null), in order to ensure that the parameter is not empty.

The communication interface design is described by the above programmed language, and any message can be transmitted through the command and message mode. In order to receive the message, the Fragment needs to follow the communication protocol designed above. The above programmatic representation is that the Fragment needs to inherit the IMessage interface and overwrite the onMessage method. After such processing, the fragment is a Fragment that inherits from the IMessage interface, and has the ability to receive messages sent by the IMessage interface.

In addition, the Fragment must receive the message forwarded by the message controller, and must register with the message controller. Only the Fragment registered with the message controller can receive the message distributed by the message controller. Among them, the specific registration process is: Fragment is a class, each class has a constructor, and registration is implemented in the constructor of the Fragment to ensure that the Fragment is actively registered in the message controller when it is instantiated.

The message registrar register (this.fragment) in the message controller is called in the constructor of the Fragment, and the Fragment object is registered in the message controller. Among them, all the Fragments registered in the message controller are in a peer relationship, that is, all the Fragments belong to an equal relationship, and multiple Fragments in the existing existence have a nested relationship, that is, multiple Fragments have a hierarchical relationship. In the present embodiment, this hierarchical relationship is reported by registering with the message controller, and all the Fragments registered in the message controller are in a peer relationship.

Based on the foregoing various embodiments, in another embodiment of the present invention, the step S2 further includes: maintaining, for all the Fragments registered to the message controller, a Fragment object for storing all the registrations in the message controller. Collection of objects.

After all the Fragments in the interface are registered in the message controller, a set of objects is maintained in the message controller, and the object set is mainly used to store all the Fragment registered in the message controller, so that the subsequent message controller can be like Fragment. Distribute the message.

On the basis of the foregoing various embodiments, in another embodiment of the present invention, the step S2 further includes: when the message controller receives the message sent by the source fragment, the message is broadcasted or peer-to-peer. Send to the destination Fragment.

When the message controller receives the message sent by the source Fragment and forwards it to the destination Fragment, the message controller can forward the message in two ways, one is to broadcast the message to the destination Fragment, and the other is to pass the peer-to-peer. The way to forward messages to the destination Fragment enables flexible distribution in a variety of ways.

In an embodiment of the present invention, in step S2, the step S2 further includes: when the message controller receives the message sent by the source fragment, and broadcasts the message to the Fragment registered with the message controller; The Fragment that receives the message determines whether the message needs to be processed according to the message command word in the message.

As described above, when the message controller forwards the message to the destination Fragment, it may be broadcast or peer-to-peer. When the message controller sends the message in a broadcast manner, the message controller broadcasts the message to the Fragment registered in the message controller when receiving the message of the Fragment, wherein the message includes the message command word and the message body. The Fragment that receives the message determines whether the message is a message required by itself according to the message command word in the message, and if it is a required message, acquires the message and processes it.

The specific process of the message controller broadcasting the message to the Fragment registered in the message controller is: the message controller traverses all the Fragment objects in the object set by means of a for loop, and extracts the Fragment one by one from the object set. Each time a Fragment object is extracted, the interface function onMessage in the Fragment object is called, and the message received from the Fragment of the sent message is passed to the interface function onMessage of the Fragment object, and the interface function onMessage is based on the message command word in the message. Determine whether the message needs to be processed, so that the process of sending a message to another Fragment is completed by the forwarding of the message controller.

In another embodiment of the present invention, the step S2 further comprises: the message controller receiving the message sent by the source Fragment, and forwarding the message to the destination Fragment according to the destination Fragment identifier in the message.

In the foregoing embodiment, the message controller forwards the message by means of a broadcast, and in this embodiment, the message controller forwards the message by means of a peer-to-peer. Specifically, when the message controller receives the message sent by the source Fragment, where the message includes the destination Fragment identifier that needs to send the message. The message controller forwards the message directly to the destination Fragment based on the destination Fragment identifier in the message.

Through the above two methods, it can be seen that the message delivery in the solution is forwarded by the message controller, and is not a way of direct communication between the traditional Fragment, and the design method of forwarding the message through the message controller is All the Fragments registered in the message controller are in a peer-to-peer relationship. When the source Fragment sends a message to the destination Fragment with a nested relationship, it is directly forwarded by the message controller to the destination Fragment, so that the message is sent and received with the Fragment. Hierarchical level is not related, and does not need to be passed through the first-level Fragment, avoiding the complicated communication problem caused by the need to send messages layer by layer.

Referring to FIG. 2, a communication system between multiple Fragments of another embodiment of the present invention is provided, including a configuration module 21, a registration module 22, and a message controller 23.

The configuration module 21 is configured to configure a message controller for all the fragments in the interface.

The registration module 22 is configured to register all the Fragments in the message controller.

The forwarding module 23 is configured to forward, by the message controller, the message of the source Fragment to the destination Fragment based on the command interface defined for each Fragment and its interface function.

The configuration module 21 is further configured to:

A command interface is configured for each Fragment, and an interface function is defined for the command interface, where the interface function includes a message command word and a message body parameter.

Referring to FIG. 3, the communication system between multiple Fragments further includes a maintenance module 24 for maintaining a Fragment object for storing all registrations in the message controller for all Fragments registered to the message controller. Collection of objects.

The message controller 23 is further specifically configured to:

When the message controller receives the message sent by the source Fragment, it sends the message to the destination Fragment in a broadcast or peer-to-peer manner.

The message controller 23 is also specifically used to:

When receiving the message sent by the source Fragment, the message is broadcast to the Fragment registered with the message controller, so that the Fragment receiving the message determines whether the message needs to be processed according to the message command word in the message. .

Referring to FIG. 4, the message controller 23 includes a traversal unit 231 and a calling unit 232, wherein the traversing unit 231 is configured to traverse all of the Fragment objects in the object set in a round-robin manner.

The calling unit 232 is configured to, when extracting a Fragment object, invoke an interface function in the Fragment object, and deliver the message to an interface function of the Fragment object, where the interface function determines according to a message command word in the message. Whether the message needs to be processed.

Referring to FIG. 5, an electronic device according to the present invention includes a processor 501, a memory 502, and a bus 503. The processor 501 and the memory 502 complete communication with each other through the bus 503. .

The processor 501 is configured to invoke program instructions in the memory 502 to perform the methods provided by the foregoing method embodiments, for example, including: configuring a message controller for all Fragment fragments in the interface, and controlling the message All Fragments are registered, wherein all registered Fragments are in an equal relationship; based on the command interface defined for each Fragment and its interface function, the message controller forwards the source Fragment message to the destination Fragment. The invention discloses a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions, the computer being capable of executing the corresponding implementation when the program instructions are executed by the computer The intelligent filtering control layout method provided by the example includes, for example, configuring a message controller for all Fragment fragments in the interface, and registering all the Fragment in the message controller, wherein all registered Fragments are in an equal relationship; For each command interface defined by each Fragment and its interface function, the message controller forwards the message of the source Fragment to the destination Fragment.

The present invention also provides a non-transitory computer readable storage medium storing computer instructions for causing a computer to execute the smart layout control method provided by the corresponding embodiment, for example, including Configuring a message controller for all Fragment fragments in the interface, and registering all Fragments in the message controller, wherein all registered Fragments are in an equal relationship; based on the command interface defined for each Fragment and its interface function, The message of the source Fragment is forwarded by the message controller to the destination Fragment.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to the program instructions. The foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

The embodiments described above are merely illustrative, wherein the units illustrated as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located in one place. Or it can be distributed to multiple network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without deliberate labor.

Through the description of the above embodiments, those skilled in the art can clearly understand that the various embodiments can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware. Based on such understanding, the above-described technical solutions may be embodied in the form of software products in essence or in the form of software products, which may be stored in a computer readable storage medium such as ROM/RAM, magnetic Discs, optical discs, etc., include instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform various embodiments of the various embodiments or embodiments.

The invention provides a communication method and system between multiple Fragment, and configures a message manager for all Fragment in the interface, and the message controller performs forwarding to implement a Fragment to send a message to another Fragment to avoid multiple Fragment The confusion of direct communication; and when there is a nested relationship between multiple Fragments, since all the Fragments registered in the message controller in this embodiment are in a peer relationship, the source Fragment has a nested relationship. When the message is sent by the Fragment, it is directly forwarded to the destination Fragment by the message controller, without the need to pass the Fragment of the first-level level, which avoids the complicated communication problem caused by the need to send messages layer by layer.

Finally, the method of the present application is only a preferred embodiment and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

A communication method between multiple Fragments, comprising:

S1, configuring a message controller for all Fragment fragments in the interface, and registering all Fragments in the message controller, wherein all registered Fragments are in an equal relationship;

S2, based on the command interface defined for each Fragment and its interface function, the message controller forwards the message of the source Fragment to the destination Fragment.
The method of communicating between multiple Fragments according to claim 1, wherein the step S2 further comprises:

A command interface is defined for each Fragment, and an interface function is defined for the command interface, and the interface function includes at least a message command word and a message body parameter.
The method of communicating between multiple Fragments according to claim 2, wherein the step S2 further comprises:

For all Fragments registered to the message controller, maintain a collection of objects in the message controller that hold all registered Fragment objects.
The method of communicating between multiple Fragments according to claim 3, wherein the step S2 further comprises:

When the message controller receives the message sent by the source Fragment, the message is sent to the destination Fragment in a broadcast manner or in a peer-to-peer manner.
The method of communicating between multiple Fragments according to claim 4, wherein the step S2 further comprises:

When the message controller receives the message sent by the source fragment, the message is broadcast to the Fragment registered with the message controller;

The Fragment receiving the message determines whether the message body in the message needs to be processed according to the message command word in the message.
The method of communicating between multiple Fragments according to claim 5, wherein the step S2 further comprises:

The message controller traverses all the Fragment objects in the object collection in a round-robin manner;

Each time a Fragment object is extracted, an interface function in the Fragment object is called, and the message is delivered to an interface function of the Fragment object, and the interface function determines whether the message needs to be in the message according to the message command word in the message. The message body is processed.
The communication method of the multi-Fragment according to claim 4, wherein the message further includes a destination Fragment identifier, and the step S2 further comprises:

The message controller receives the message sent by the source Fragment, and forwards the message to the destination Fragment according to the destination Fragment identifier in the message.
A communication system between multiple Fragments, characterized in that

a configuration module configured to configure a message controller for all the Fragments in the interface;

a registration module for registering all Fragments in the message controller, wherein all registered Fragments are in an equal relationship;

The forwarding module is configured to forward the message of the source Fragment to the destination Fragment by the message controller based on the command interface defined for each Fragment and its interface function.
An electronic device, comprising:

At least one processor, at least one memory, a communication interface, and a bus;

Wherein the processor, the memory, and the communication interface complete communication with each other through the bus;

The communication interface is used for information transmission between the device and a communication device of the toy control system;

The memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the method of any of claims 1-7.
A computer program product, comprising: a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions, when the program instructions are executed by a computer, The computer instructions cause the computer to perform the method of any of claims 1-7.
A non-transitory computer readable storage medium, wherein the non-transitory computer readable storage medium stores computer instructions, the computer instructions causing the computer to perform the method of any of claims 1-7 method.