CN111857985A - Calling method and device of browser plug-in, storage medium and terminal - Google Patents
Calling method and device of browser plug-in, storage medium and terminal Download PDFInfo
- Publication number
- CN111857985A CN111857985A CN202010514595.8A CN202010514595A CN111857985A CN 111857985 A CN111857985 A CN 111857985A CN 202010514595 A CN202010514595 A CN 202010514595A CN 111857985 A CN111857985 A CN 111857985A
- Authority
- CN
- China
- Prior art keywords
- plug
- calling
- browser page
- browser
- request
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application discloses a method and a device for calling a browser plug-in, a storage medium and a terminal, and belongs to the field of computers. According to the method and the device, the coupling degree between the plug-ins and the browser is reduced, developers do not need to consider the types of the browsers when developing the plug-ins for a certain page of the browser, namely, a set of plug-ins do not need to be developed for each type of browser independently, so that a set of plug-ins can be developed for multiple types of browsers together, development cost can be reduced, and development efficiency can be improved.
Description
Technical Field
The present application relates to the field of computers, and in particular, to a method and an apparatus for invoking a browser plug-in, a storage medium, and a terminal.
Background
The plug-in is an application program with a specific format set in a browser, and the browser can directly call the plug-in to process a specific type of file, such as: a Flash plug-in, a Realplay plug-in, an MMS plug-in, an ActiveX plug-in and the like can be arranged in the browser. In the related art, different types of browsers support and manage plug-ins differently, for example: the IE browser calls and manages the plug-in set in the browser page in an ActiveX and com component mode; the latest Chrome browser uses a PPAPI mode to manage and call the plug-in arranged in the browser page; the early Chrome browser manages and calls the plug-in an NPAPI mode; the Firefox browser is the same as the Chrome browser. Therefore, different browsers with different types and versions call and manage different plug-ins, and developers of the plug-ins must develop different plug-ins for different types of browsers to adapt to the different types of browsers.
Disclosure of Invention
The method, the device, the storage medium and the terminal for calling the browser plug-ins can solve the problems of high development cost and low efficiency caused by the fact that different plug-ins are developed for different types of browsers in the related technology. The technical scheme is as follows:
in a first aspect, an embodiment of the present application provides a method for calling a browser plug-in, where the method includes:
receiving a plug-in calling request from a browser page; the plug-in calling request carries the identification of the browser page and the identification of the plug-in;
after the browser page is verified to pass, inquiring the state of the plug-in;
when the plug-in is in a registered state and a running state, sending the plug-in calling request to the plug-in;
receiving a plug-in calling response returned by the plug-in response to the plug-in calling request;
and sending the plug-in calling response to the browser page.
In a second aspect, an embodiment of the present application provides a calling apparatus for a browser plug-in, where the calling apparatus includes:
the receiving and sending unit is used for receiving a plug-in calling request from a browser page; the plug-in calling request carries the identification of the browser page and the identification of the plug-in;
The processing unit is used for inquiring the state of the plug-in after the browser page is verified to pass;
the transceiver unit is further configured to send the plug-in call request to the plug-in when the plug-in is registered and is running;
the transceiving unit is further used for receiving a plug-in calling response returned by the plug-in response to the plug-in calling request;
the receiving and sending unit is further configured to send the plug-in call response to the browser page.
In a third aspect, embodiments of the present application provide a computer storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the above-mentioned method steps.
In a fourth aspect, an embodiment of the present application provides a terminal, which may include: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the above-mentioned method steps.
The beneficial effects brought by the technical scheme provided by some embodiments of the application at least comprise:
when a page in a browser needs to call a plug-in, the browser page sends a plug-in calling request to a plug-in management center, the plug-in management center inquires the state of the plug-in needing to be called after verifying that the browser page identity is legal, when the plug-in is registered and runs, the plug-in calling request is forwarded to the plug-in, and then the plug-in calling response of the plug-in is forwarded to the browser page for display.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1A is a diagram of a network architecture provided in an embodiment of the present application;
FIG. 1B is a schematic structural diagram of an interposer provided in an embodiment of the present application;
FIG. 2 is a flowchart illustrating a method for invoking a browser plug-in according to an embodiment of the present disclosure;
FIG. 3 is a schematic diagram of an apparatus according to an embodiment of the present disclosure;
fig. 4 is another schematic structural diagram of an apparatus provided in the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
Referring to fig. 1A, a network architecture diagram provided for an embodiment of the present application includes a browser page, a plug-in management center, and a plug-in.
The browser page is an area for displaying other information such as characters, images or videos in the browser, and a user can perform interactive operation in the browser page; the type of the browser is not limited in the embodiments of the present application, and may be an IE browser, a Chrome browser, a Firefox browser, or a safari browser.
The plug-in management center is a transfer station for communication between the browser page and the plug-in, and the plug-in management center may be software, for example: the plug-in management center is an application program which is independent of the browser and is deployed in an operating system of the terminal, and the plug-in management center can also be a module built in the operating system.
The plug-in is an application program in a browser page for processing a specific file, for example: the plug-in includes: flash plug-ins, RealPlayer plug-ins, MMS plug-ins, MIDI staff plug-ins, ActiveX plug-ins, etc. The plug-in may also set a URL (Uniform Resource Locator) address so that the plug-in management center can launch or wake the plug-in through the URL address.
In this embodiment, the browser page, the plug-in management center, and the plug-in may communicate with each other by using a TCP/IP protocol, for example: the web browser comprises a browser page, a plug-in management center, a web socket server and a socket server, wherein the browser page is provided with the web socket client, the plug-in management center is provided with the socket client, the web socket client in the browser page and the web socket server in the plug-in management center are in communication connection, and the socket server in the plug-in management center and the socket client in the plug-in management center are in communication connection.
As shown in fig. 1B, the plug-in is configured with a function module, a socket client and a URL address, the function module is used to implement a specific function, the socket client is used to implement communication between the plug-in management centers, and the URL address is used to wake up or start the plug-in through the URL address when the plug-in is not running. Further, the plug-in may also be configured with an external configuration file, which is used to configure parameters of the plug-in, such as: the parameters of the plug-in include: one or more of the switch parameter, the performance parameter, and the address of the plug-in management center, where the external configuration file may be set independently of the plug-in, or may be directly compiled into the plug-in, and this embodiment is not limited.
The plug-in management center can be configured with a registration center, a message center and a log center besides a websocket server and a socket server, wherein the functions of the registration center comprise the registration of the plug-ins and the recording of the registered plug-ins; the message center is used for constructing a message queue transmitted to the browser page or the plug-in, the message queue transmitted to the browser page is deployed in the websocket server, and the message queue transmitted to the plug-in is deployed in the socket server. The log center is used for recording the calling record of the plug-in and the log generated by the communication between the plug-in management center and the browser page and between the plug-in management center and the plug-in. After the plug-in management center opens the websocket server, monitoring a specific port, and receiving a message sent by a browser page through the port; meanwhile, after the socket server is started, the plug-in management center monitors a specific port and receives a message from the plug-in through the port.
The method for calling the browser plug-in provided by the embodiment of the present application will be described in detail below with reference to fig. 2. The calling device of the browser plug-in the embodiment of the application may be a terminal.
Referring to fig. 2, a flowchart of a method for invoking a browser plug-in is provided in an embodiment of the present application. As shown in fig. 2, the method of the embodiment of the present application may include the steps of:
s201, receiving a plug-in calling request from a browser page.
When the browser page needs to communicate with the plug-in, the browser page sends a plug-in calling request to the plug-in management center, wherein the plug-in calling request carries the identifier of the browser page and the identifier of the plug-in, and the plug-in calling request is used for calling the plug-in. The identity of the browser page is used to uniquely represent the identity of the browser page, with different browser pages having different identities. The identity of the plug-in is used to uniquely represent the identity of the plug-in, with different plugs-ins having different identities.
S202, after the browser page is verified to pass, the state of the plug-in is inquired.
The plug-in management center prestores or preconfigures a database comprising a plurality of browser page identifications and a plurality of plug-in state identifications, and the browser page identifications in the database are legal browser page identifications. The plug-in management center judges whether a browser page identifier carried in the plug-in calling request exists in the database, and if yes, the verification of the browser page is passed; if not, the verification browser page is not passed. After the browser page is verified to pass, inquiring the state of the plug-in the database according to the state identification, wherein the state of the plug-in comprises two dimensions of a registration state and an operation state, the registration state is used for indicating whether the plug-in is registered in a plug-in management center in advance, and the operation state indicates whether the plug-in operates; the registration state includes registered and unregistered, and the operation state includes operated or not operated. For example: when the flag indicates the operation state, a bit is used to indicate that the plug-in is operated when the value of the bit is 1, and that the plug-in is not operated when the value of the bit is 0.
And S203, when the plug-in is registered and operated, sending a plug-in calling request to the plug-in.
When the plug-in management center inquires that the plug-in is registered and operates, a plug-in calling request is sent to the plug-in, wherein the plug-in calling request is used for indicating the plug-in to execute a specific function.
In one possible implementation, when the plug-in is unregistered, an unregistered message is sent to the browser page.
The plug-in management center can inquire a corresponding state identifier in the database according to the identifier of the plug-in, and when the state of the plug-in is determined to be unregistered according to the state identifier, the plug-in management center sends an unregistered message to a browser page so as to display the unregistered message on the browser page.
In one possible implementation mode, when the plug-in is registered and does not run, whether the plug-in is configured with a URL (uniform resource locator) address is judged, and if so, the plug-in is started based on the URL address; after the plug-in is successfully started, sending the plug-in calling request to the plug-in, and receiving a plug-in calling response returned by the plug-in response to the plug-in calling request; and sending the plug-in calling response to the browser page.
The URL address is used for starting the plug-in unit, so that the plug-in unit is in the running state, and the browser page can call the plug-in unit to execute corresponding functions conveniently.
Further, when the plug-in is not configured with the URL address for starting, a prompt message for prompting the user to manually start the plug-in is displayed on the browser page, so that the user manually starts the plug-in to make the running state of the plug-in be running, and the operation of manually starting the plug-in includes but is not limited to: the operation is performed by a mouse, by a keyboard, or by a touch screen.
In a possible implementation manner, before receiving a plug-in call request of a browser page, the method further includes:
receiving a registration request message from a browser page; wherein, the registration request message carries the identification of the plug-in and the identification of the browser page;
inquiring whether the plug-in is registered;
if not, recording the identification of the plug-in, and marking the state of the plug-in as registered.
Further, after the plug-in registration is successful, whether the plug-in is configured with the URL address for starting is judged, and if yes, the URL address of the plug-in is obtained, and the URL address of the plug-in is stored.
The plugin management center prestores the identification of the registered plugin, judges whether the plugin identification carried in the registration request message is the prestored plugin identification, if so, indicates that the plugin is registered, and if not, indicates that the plugin is not registered.
And S204, receiving a plug-in calling response returned by the plug-in response to the plug-in calling request.
The plug-in executes the corresponding function to generate an execution result, and the plug-in calls a response to carry the execution result, for example: when the plug-in is a Flash plug-in, the execution result is animation data of a Flash file; when the plug-in is a RealPlayer plug-in, the execution result is video data. And the plug-in management center receives a plug-in calling response of the execution result of the write returned by the plug-in calling request.
S205, sending the plug-in calling response to the browser page.
The plug-in management center sends the plug-in call response to the browser page, and instructs the browser page to analyze an execution result in the plug-in call response, for example: when the execution result is animation data, playing the animation data on the browser page; and when the execution result is the video data, playing the video data on the browser page.
By implementing the embodiment of the application, when a page in a browser needs to call a plug-in, the browser page sends a plug-in calling request to a plug-in management center, the plug-in management center inquires the state of the plug-in needing to be called after verifying that the browser page is legal in identity, when the plug-in is registered and is operated, the plug-in calling request is forwarded to the plug-in, and then the plug-in calling response of the plug-in is forwarded to the browser page for display.
The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.
Referring to fig. 3, a schematic structural diagram of a calling device of a browser plug-in according to an exemplary embodiment of the present application is shown. Hereinafter referred to as device 3, the device 3 may be implemented by software, hardware or a combination of both as all or part of a plug-in management center or a terminal. The apparatus 3 comprises: a transceiving unit 301 and a processing unit 302.
A transceiving unit 301, configured to receive a plug-in call request from a browser page; the plug-in calling request carries the identification of the browser page and the identification of the plug-in;
the processing unit 302 is configured to query the state of the plug-in after the browser page is verified to pass;
the transceiving unit 301 is further configured to send the plug-in call request to the plug-in when the plug-in is registered and is running;
the transceiving unit 301 is further configured to receive a plug-in call response returned by the plug-in response to the plug-in call request;
the transceiving unit 301 is further configured to send the plug-in call response to the browser page.
In some possible embodiments, the transceiving unit 301 is further configured to: when the plug-in is unregistered, sending an unregistered message to the browser page; wherein the unregistered message is used for indicating that the plug-in is in an unregistered state.
In some possible embodiments, the processing unit 302 is further configured to: when the plug-in is registered but not operated, judging whether the plug-in is configured with a URL address or not;
if so, starting the plug-in based on the URL address;
the transceiver unit 301 is further configured to send the plug-in call request to the plug-in after the plug-in is successfully started;
receiving a plug-in calling response returned by the plug-in response to the plug-in calling request;
and sending the plug-in calling response to the browser page.
In some possible embodiments, the processing unit 302 is further configured to: and when the plug-in is not configured with the URL address for starting the plug-in, displaying a prompt message for prompting a user to manually start the plug-in on the browser page.
In some possible embodiments, the transceiving unit 301 is further configured to: receiving a registration request message from the browser page; wherein, the registration request message carries the identification of the plug-in and the identification of the plug-in;
The processing unit 302 is further configured to: inquiring whether the plug-in is in a registered state;
if not, recording the identification of the plug-in and marking the state of the plug-in as registered.
In some possible embodiments, the processing unit 302 is further configured to: and when the plug-in is configured with the URL address for starting, acquiring the URL address of the plug-in and storing the URL address of the plug-in.
In some possible embodiments, the transceiver unit 301 performs the receiving of the plug-in invocation request from the browser page, including:
a websocket-based server receives a plug-in calling request sent by the browser page based on the websocket client;
wherein sending the plug-in invocation request to the plug-in comprises:
and sending the plug-in calling request to a socket client of the plug-in based on the socket server.
It should be noted that, when the apparatus 3 provided in the foregoing embodiment executes the method for calling the browser plug-in, the division of the function modules is merely exemplified, and in practical applications, the function distribution may be completed by different function modules according to needs, that is, the internal structure of the device is divided into different function modules, so as to complete all or part of the functions described above. In addition, the calling method embodiment of the browser plug-in provided by the above embodiment belongs to the same concept, and details of the implementation process are referred to as the method embodiment, which are not described herein again.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
An embodiment of the present application further provides a computer storage medium, where the computer storage medium may store a plurality of instructions, where the instructions are suitable for being loaded by a processor and executing the method steps in the embodiment shown in fig. 2, and a specific execution process may refer to a specific description of the embodiment shown in fig. 2, which is not described herein again.
The present application further provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the method for invoking the browser plug-in according to the above embodiments.
Fig. 4 is a schematic structural diagram of a calling apparatus of a browser plug-in provided in an embodiment of the present application, which is hereinafter referred to as an apparatus 4 for short, where the apparatus 4 may be integrated in the aforementioned plug-in management center or terminal, as shown in fig. 4, the apparatus includes: memory 402, processor 401, and transceiver 403.
The memory 402 may be a separate physical unit, and may be connected to the processor 401 and the transceiver 403 via a bus. The memory 402, processor 401, transceiver 403 may also be integrated, implemented in hardware, etc.
The memory 402 is used for storing a program implementing the above method embodiment, or various modules of the apparatus embodiment, which is called by the processor 401 to perform the operations of the above method embodiment.
In some embodiments, device 4 may also include input devices including, but not limited to, a keyboard, a mouse, a touch panel, a camera, and a microphone; the output device includes, but is not limited to, a display screen.
Alternatively, when part or all of the distributed task scheduling method of the above embodiments is implemented by software, the apparatus may also include only a processor. The memory for storing the program is located outside the device and the processor is connected to the memory by means of circuits/wires for reading and executing the program stored in the memory.
The processor may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of a CPU and an NP.
The processor may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), or any combination thereof.
The memory may include volatile memory (volatile memory), such as random-access memory (RAM); the memory may also include a non-volatile memory (non-volatile memory), such as a flash memory (flash memory), a Hard Disk Drive (HDD) or a solid-state drive (SSD); the memory may also comprise a combination of memories of the kind described above.
Wherein the processor 401 calls the program code in the memory 402 for performing the following steps:
receiving a plug-in invocation request from a browser page through the transceiver 403; the plug-in calling request carries the identification of the browser page and the identification of the plug-in;
after the browser page is verified to pass, inquiring the state of the plug-in;
sending the plug-in invocation request to the plug-in through the transceiver 403 when the plug-in is registered and run;
receiving, by the transceiver 403, a plug-in invocation response returned by the plug-in response to the plug-in invocation request;
the plug-in invocation response is sent to the browser page through the transceiver 403.
In some possible embodiments, the processor 401 is further configured to perform: sending an unregistered message to the browser page when the plug-in is unregistered through the transceiver 403; wherein the unregistered message is used for indicating that the plug-in is in an unregistered state.
In some possible embodiments, the processor 401 is further configured to perform:
when the plug-in is registered but not operated, judging whether the plug-in is configured with a URL address or not;
if so, starting the plug-in based on the URL address;
sending the plug-in calling request to the plug-in through the transceiver 403 after the plug-in is successfully started;
receiving a plug-in calling response returned by the plug-in response to the plug-in calling request;
and sending the plug-in calling response to the browser page.
In some possible embodiments, the processor 401 is further configured to perform:
and when the plug-in is not configured with the URL address for starting the plug-in, displaying a prompt message for prompting a user to manually start the plug-in on the browser page.
In some possible embodiments, the processor 401 is further configured to perform:
receiving a registration request message from the browser page through the transceiver 403; wherein, the registration request message carries the identification of the plug-in and the identification of the plug-in;
inquiring whether the plug-in is in a registered state;
if not, recording the identification of the plug-in and marking the state of the plug-in as registered.
In some possible embodiments, the processor 401 is further configured to perform:
when the plug-in is configured with a URL address for startup, the URL address of the plug-in is obtained, and stored by the memory 402.
In some possible embodiments, the receiving a plug-in invocation request from a browser page includes:
a websocket-based server receives a plug-in calling request sent by the browser page based on the websocket client;
wherein sending the plug-in invocation request to the plug-in comprises:
and sending the plug-in calling request to a socket client of the plug-in based on the socket server.
The embodiment of the application further provides a computer storage medium, in which a computer program is stored, where the computer program is used to execute the method for calling the browser plug-in provided by the above embodiment.
The embodiment of the present application further provides a computer program product containing instructions, which when run on a computer, causes the computer to execute the method for calling the browser plug-in provided by the foregoing embodiment.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Claims (10)
1. A calling method of a browser plug-in is characterized by comprising the following steps:
receiving a plug-in calling request from a browser page; the plug-in calling request carries the identification of the browser page and the identification of the plug-in;
after the browser page is verified to pass, inquiring the state of the plug-in;
when the plug-in is registered and operated, sending the plug-in calling request to the plug-in;
receiving a plug-in calling response returned by the plug-in response to the plug-in calling request;
and sending the plug-in calling response to the browser page.
2. The calling method of claim 1, further comprising:
when the plug-in is unregistered, sending an unregistered message to the browser page; wherein the unregistered message is used for indicating that the plug-in is in an unregistered state.
3. The calling method of claim 1, further comprising:
when the plug-in is registered but not operated, judging whether the plug-in is configured with a URL address or not; wherein the URL address is used to launch the plug-in;
if so, starting the plug-in based on the URL address;
after the plug-in is successfully started, sending the plug-in calling request to the plug-in;
receiving a plug-in calling response returned by the plug-in response to the plug-in calling request;
and sending the plug-in calling response to the browser page.
4. The calling method of claim 3, further comprising:
and when the plug-in is not configured with the URL address for starting the plug-in, displaying a prompt message for prompting a user to manually start the plug-in on the browser page.
5. The calling method according to claim 1, wherein before receiving the plug-in call request from the browser page, the method further comprises:
receiving a registration request message from the browser page; wherein, the registration request message carries the identification of the plug-in and the identification of the plug-in;
inquiring whether the plug-in is in a registered state;
If not, recording the identification of the plug-in and marking the state of the plug-in as registered.
6. The calling method of claim 5, further comprising:
and when the plug-in is configured with the URL address, acquiring the URL address of the plug-in and storing the URL address of the plug-in.
7. The calling method according to claim 1, wherein the receiving a plug-in call request from a browser page comprises:
a websocket-based server receives a plug-in calling request sent by the browser page based on the websocket client;
wherein sending the plug-in invocation request to the plug-in comprises:
and sending the plug-in calling request to a socket client of the plug-in based on the socket server.
8. An apparatus for invoking a browser plug-in, the apparatus comprising:
the receiving and sending unit is used for receiving a plug-in calling request from a browser page; the plug-in calling request carries the identification of the browser page and the identification of the plug-in;
the processing unit is used for inquiring the state of the plug-in after the browser page is verified to pass;
the transceiver unit is further configured to send the plug-in call request to the plug-in when the plug-in is registered and is running;
The transceiving unit is further used for receiving a plug-in calling response returned by the plug-in response to the plug-in calling request;
the receiving and sending unit is further configured to send the plug-in call response to the browser page.
9. A computer storage medium, characterized in that it stores a plurality of instructions adapted to be loaded by a processor and to carry out the method steps according to any one of claims 1 to 7.
10. A terminal, comprising: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the method steps of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010514595.8A CN111857985A (en) | 2020-06-08 | 2020-06-08 | Calling method and device of browser plug-in, storage medium and terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010514595.8A CN111857985A (en) | 2020-06-08 | 2020-06-08 | Calling method and device of browser plug-in, storage medium and terminal |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111857985A true CN111857985A (en) | 2020-10-30 |
Family
ID=72987505
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010514595.8A Pending CN111857985A (en) | 2020-06-08 | 2020-06-08 | Calling method and device of browser plug-in, storage medium and terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111857985A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115291968A (en) * | 2022-08-01 | 2022-11-04 | 国投智能科技有限公司 | Service processing method, system and computer equipment |
| CN115328576A (en) * | 2022-09-03 | 2022-11-11 | 郭云开 | Device and method for loading plug-in of browser |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101233494A (en) * | 2005-07-29 | 2008-07-30 | 株式会社爱可信 | Plug-in module execution method, browser execution method, mailer execution method, program, terminal device, and computer-readable recording medium containing page data |
| US20090019151A1 (en) * | 2007-07-10 | 2009-01-15 | Stavrakos Nicholas J | Method for media discovery |
| CN103023976A (en) * | 2012-11-19 | 2013-04-03 | 北京奇虎科技有限公司 | Device and method for extending browser application plug-ins |
| US20130191526A1 (en) * | 2011-03-14 | 2013-07-25 | Tencent Technology Shenzhen Company Limited | Open plug-in management platform and plug-in management method implemented on browser |
| WO2015055073A1 (en) * | 2013-10-18 | 2015-04-23 | 北京奇虎科技有限公司 | Method, apparatus and system for reminding message |
| CN104978199A (en) * | 2015-07-10 | 2015-10-14 | 无锡天脉聚源传媒科技有限公司 | Plug-in application method and device used for multiple browsers |
| CN105471824A (en) * | 2014-09-03 | 2016-04-06 | 阿里巴巴集团控股有限公司 | Method, device and system for invoking local service assembly by means of browser |
| US20170289315A1 (en) * | 2014-12-19 | 2017-10-05 | Alibaba Group Holding Limited | Data communication method and apparatus |
-
2020
- 2020-06-08 CN CN202010514595.8A patent/CN111857985A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101233494A (en) * | 2005-07-29 | 2008-07-30 | 株式会社爱可信 | Plug-in module execution method, browser execution method, mailer execution method, program, terminal device, and computer-readable recording medium containing page data |
| US20090019151A1 (en) * | 2007-07-10 | 2009-01-15 | Stavrakos Nicholas J | Method for media discovery |
| US20130191526A1 (en) * | 2011-03-14 | 2013-07-25 | Tencent Technology Shenzhen Company Limited | Open plug-in management platform and plug-in management method implemented on browser |
| CN103023976A (en) * | 2012-11-19 | 2013-04-03 | 北京奇虎科技有限公司 | Device and method for extending browser application plug-ins |
| WO2015055073A1 (en) * | 2013-10-18 | 2015-04-23 | 北京奇虎科技有限公司 | Method, apparatus and system for reminding message |
| CN105471824A (en) * | 2014-09-03 | 2016-04-06 | 阿里巴巴集团控股有限公司 | Method, device and system for invoking local service assembly by means of browser |
| US20170289315A1 (en) * | 2014-12-19 | 2017-10-05 | Alibaba Group Holding Limited | Data communication method and apparatus |
| CN104978199A (en) * | 2015-07-10 | 2015-10-14 | 无锡天脉聚源传媒科技有限公司 | Plug-in application method and device used for multiple browsers |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115291968A (en) * | 2022-08-01 | 2022-11-04 | 国投智能科技有限公司 | Service processing method, system and computer equipment |
| CN115291968B (en) * | 2022-08-01 | 2024-02-23 | 国投智能科技有限公司 | Service processing method, system and computer equipment |
| CN115328576A (en) * | 2022-09-03 | 2022-11-11 | 郭云开 | Device and method for loading plug-in of browser |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108460115B (en) | Message pushing method and device, computer equipment and storage medium | |
| CN107133180B (en) | Dynamic page testing method, testing device and storage medium | |
| CN111475376B (en) | Method, apparatus, computer device and storage medium for processing test data | |
| CN108228444B (en) | Test method and device | |
| CN110365724B (en) | Task processing method and device and electronic equipment | |
| CN113360301B (en) | Message transmission system and method | |
| CN109040263B (en) | Service processing method and device based on distributed system | |
| CN111400246B (en) | Asynchronous file import method, device, computer equipment and storage medium | |
| CN113806037A (en) | Service calling method and device, storage medium and electronic equipment | |
| CN112714158A (en) | Transaction processing method, relay network, cross-link gateway, system, medium, and device | |
| CN111857985A (en) | Calling method and device of browser plug-in, storage medium and terminal | |
| CN108427639B (en) | Automated testing method, application server and computer readable storage medium | |
| CN108345508B (en) | Interface call testing method and device | |
| CN111488286B (en) | Method and device for independently developing Android modules | |
| CN111327680B (en) | Authentication data synchronization method, device, system, computer equipment and storage medium | |
| CN112860398A (en) | Data processing method, device, equipment and medium based on rule engine | |
| CN114070824B (en) | Registration method of Internet of things equipment, registration cloud server and medium | |
| CN114968822A (en) | Interface testing method and device, computer equipment and storage medium | |
| CN114116544A (en) | Method, device and equipment for acquiring slot information and storage medium | |
| CN112702436A (en) | Flow recording method and device, computer equipment and storage medium | |
| CN112261051B (en) | User registration method, device and system | |
| CN117883789B (en) | Data acquisition method, apparatus, device, readable storage medium, and program product | |
| CN116132214B (en) | Event transmission method, device, equipment and medium based on event bus model | |
| CN115426394A (en) | Communication connection method, communication connection device, electronic equipment and storage medium | |
| CN116795607A (en) | Page screenshot verification method and device, storage medium and electronic equipment |
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 |