Method and system for starting application
A first local application starts a websocket and attempts to connect, with the websocket, to a local socket started by a second local application. If the first local application connects to the local socket, stopping a jump to a boot page for downloading the second local application.
1. A computer-implemented method, comprising:
starting, by a first local application, a websocket;
attempting, by the first local application, to connect, with the websocket, to a local socket started by a second local application, and wherein the attempting comprising, during a predetermined time period:
iteratively using a set of ports in a predetermined port group to attempt to connect to the local socket;
determining whether the first local application connects, with the websocket, to the local socket during the predetermined time period;
in response to a negative determination, initiating a jump to a boot page for downloading the second local application; and
in response to a positive determination, stopping the jump to the boot page for downloading the second local application.
2. The computer-implemented method of claim 1 , wherein the first local application comprises a browser application or a local application integrated with a Web View component.
3. The computer-implemented method of claim 1 , wherein, when a link to a web page is triggered and opened:
assembling, by the first local application, parameters comprising a web page address as a uniform resource indicator (URI), and
invoking, by the first local application, the second local application corresponding to the URI.
4. The computer-implemented method of claim 1 , wherein the start of the websocket by the first local application and the attempt to connect, with the websocket, to the local socket by the first local application occurs after a predetermined duration of time since the web page is opened.
5. The computer-implemented method of claim 1 , further comprising:
if the first local application fails to connect, with the websocket, to the local socket, jumping to the boot page for downloading the second local application; or
if the first local application receives an error prompt when connecting, with the websocket, to the local socket, jumping to the boot page for downloading the second local application.
6. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
starting, by a first local application, a websocket;
attempting, by the first local application, to connect, with the websocket, to a local socket started by a second local application, and wherein the attempting comprising, during a predetermined time period:
iteratively using a set of ports in a predetermined port group to attempt to connect to the local socket;
determining whether the first local application connects, with the websocket, to the local socket during the predetermined time period;
in response to a negative determination, initiating a jump to a boot page for downloading the second local application; and
in response to a positive determination, stopping the jump to the boot page for downloading the second local application.
7. The non-transitory, computer-readable medium of claim 6 , wherein the first local application comprises a browser application or a local application integrated with a Web View component.
8. The non-transitory, computer-readable medium of claim 6 , wherein, when a link to a web page is triggered and opened:
assembling, by the first local application, parameters comprising a web page address as a uniform resource indicator (URI), and
invoking, by the first local application, the second local application corresponding to the URI.
9. The non-transitory, computer-readable medium of claim 6 , wherein the start of the websocket by the first local application and the attempt to connect, with the websocket, to the local socket by the first local application occurs after a predetermined duration of time since the web page is opened.
10. The non-transitory, computer-readable medium of claim 6 , wherein the operations further comprise:
if the first local application fails to connect, with the websocket, to the local socket, jumping to the boot page for downloading the second local application; or
if the first local application receives an error prompt when connecting, with the websocket, to the local socket, jumping to the boot page for downloading the second local application.
11. A computer-implemented system, comprising:
one or more computers; and
one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
starting, by a first local application, a websocket;
attempting, by the first local application, to connect, with the websocket, to a local socket started by a second local application, and wherein the attempting comprising, during a predetermined time period:
iteratively using a set of ports in a predetermined port group to attempt to connect to the local socket;
determining whether the first local application connects, with the websocket, to the local socket during the predetermined time period;
in response to a negative determination, initiating a jump to a boot page for downloading the second local application; and
in response to a positive determination, stopping the jump to the boot page for downloading the second local application.
12. The computer-implemented system of claim 11 , wherein the first local application comprises a browser application or a local application integrated with a Web View component.
13. The computer-implemented system of claim 11 , wherein, when a link to a web page is triggered and opened:
assembling, by the first local application, parameters comprising a web page address as a uniform resource indicator (URI), and
invoking, by the first local application, the second local application corresponding to the URI.
14. The computer-implemented system of claim 11 , wherein the start of the websocket by the first local application and the attempt to connect, with the websocket, to the local socket by the first local application occurs after a predetermined duration of time since the web page is opened.
15. The computer-implemented system of claim 11 , wherein the operations further comprise: if the first local application fails to connect, with the websocket, to the local socket, jumping to the boot page for downloading the second local application; or
if the first local application receives an error prompt when connecting, with the websocket, to the local socket, jumping to the boot page for downloading the second local application.