CN110557507B - File transmission method and device, electronic equipment and computer readable storage medium - Google Patents
File transmission method and device, electronic equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN110557507B CN110557507B CN201910840048.6A CN201910840048A CN110557507B CN 110557507 B CN110557507 B CN 110557507B CN 201910840048 A CN201910840048 A CN 201910840048A CN 110557507 B CN110557507 B CN 110557507B
- Authority
- CN
- China
- Prior art keywords
- application program
- file
- file transmission
- target plug
- application
- 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
-
- 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/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
Abstract
The application provides a file transmission method, a file transmission device and electronic equipment, wherein the file transmission method is applied to the electronic equipment, a first application program and a second application program are installed in the electronic equipment, a protocol used by the second application program is a secure file transfer protocol, and the file transmission method comprises the following steps: receiving a file transfer request through a first application; after receiving a file transmission request, calling a target plug-in through a first application program; and starting the second application program through the target plug-in so as to execute the file transmission request through the second application program. According to the method, the security of file transmission can be improved.
Description
Technical Field
The application relates to the technical field of computers, in particular to a file transmission method and device and electronic equipment.
Background
The existing file transmission method mainly comprises the following steps: uploading the file by using a JS (JavaScript) component; and calling the plug-in by the browser, and uploading the file by using the plug-in. However, the file transfer efficiency of these two file uploading methods is relatively low, and the file uploading using the plug-in of the browser may cause a problem of security of the browser.
Disclosure of Invention
In view of the above, an object of the present invention is to provide a file transmission method, a file transmission device and an electronic device. The effect of relatively safely transmitting files can be achieved.
In a first aspect, an embodiment of the present application provides a file transmission method, which is applied to an electronic device, where a first application program and a second application program are installed in the electronic device, and a protocol used by the second application program is a secure file transfer protocol, where the method includes:
receiving a file transfer request through a first application;
after receiving the file transmission request, calling a target plug-in through the first application program;
and starting the second application program through the target plug-in so as to process the file transmission request through the second application program.
With reference to the first aspect, an embodiment of the present application provides a first possible implementation manner of the first aspect, where: the method further comprises the following steps:
when the page where the file transmission request is received is entered for the first time, outputting a prompt message for judging whether the target plug-in is installed;
and when receiving a confirmation message input aiming at the prompt message, installing the target plug-in, and storing the executable file of the target plug-in a specified storage folder.
According to the file transmission method provided by the embodiment of the application, the prompt message is output before the plug-in is installed, so that a user can know the plug-in which is being safely installed, and the safety of plug-in installation can be improved.
With reference to the first possible implementation manner of the first aspect, an embodiment of the present application provides a second possible implementation manner of the first aspect, where: the step of storing the executable file of the target plug-in a designated storage folder comprises the following steps:
and storing the executable file of the target plug-in a system folder of the Windows operating system.
With reference to the first aspect, an embodiment of the present application provides a third possible implementation manner of the first aspect, where the step of calling a target plug-in through the first application includes:
creating a target object of the target plug-in based on the first application program;
calling a specified method in the target object to start the target plug-in;
the step of processing the file transfer request by the second application includes: and starting the second application program through the specified method so as to process the file transmission request through the second application program.
With reference to the first aspect, an embodiment of the present application provides a fourth possible implementation manner of the first aspect, where the step of processing, by the second application program, the file transfer request includes:
acquiring user identity authentication information acquired by the target plug-in from the first application program through the second application program;
logging in a target server with the user identity authentication information through the second application program;
and uploading the transmission file corresponding to the file transmission request to the target server through the second application program.
With reference to the first aspect, an embodiment of the present application provides a fifth possible implementation manner of the first aspect, where the first application is a browser.
According to the file transmission method, the browser is used as a tool capable of accessing the servers in the wide area network, access of more servers can be achieved, the second application program is called through the plug-in to achieve file uploading in the environment where the browser can access, and under the condition that the safety of the browser is guaranteed, file uploading efficiency is higher and the file uploading is safer.
With reference to the first aspect or any one of the possible implementation manners of the first aspect, an embodiment of the present application provides a sixth possible implementation manner of the first aspect, where the second application is a WinSCP client.
In the file transmission method provided by the embodiment of the application, the WinSCP client serves as a client using a secure file transfer protocol, and a file uploading mode through the client is safer.
In a second aspect, an embodiment of the present application further provides a file transmission apparatus, which is applied to an electronic device, where a first application program and a second application program are installed in the electronic device, and a protocol used by the second application program is a secure file transfer protocol, and the apparatus includes:
the receiving module is used for receiving a file transmission request through a first application program;
the calling module is used for calling a target plug-in through the first application program after receiving the file transmission request;
and the starting module is used for starting the second application program through the target plug-in and processing the file transmission request through the second application program.
In a third aspect, an embodiment of the present application further provides an electronic device, including: a processor, a memory storing machine-readable instructions executable by the processor, the machine-readable instructions, when executed by the processor, performing the steps of the method of the first aspect described above, or any possible implementation of the first aspect, when the electronic device is run.
In a fourth aspect, this embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to perform the steps of the method in the first aspect or any one of the possible implementation manners of the first aspect.
According to the file transmission method and device, the electronic device and the computer readable storage medium, the file transmission request is executed by calling the second application program using the secure file transfer protocol, and compared with the JS component file uploading and the plug-in file uploading of the browser in the prior art, the file transmission method and device, the electronic device and the computer readable storage medium can improve the file uploading efficiency and stability through the secure file transfer protocol uploading.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a block diagram of an electronic device according to an embodiment of the present disclosure.
Fig. 2 is a flowchart of a file transfer method according to an embodiment of the present application.
Fig. 3 is a detailed flowchart of step 203 of the file transmission method according to the embodiment of the present application.
Fig. 4 is a schematic functional module diagram of a file transfer device according to an embodiment of the present application.
Detailed Description
The technical solution in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
The existing file uploading technology mainly includes two architectures: a C/S (Client-Server) mode and a B/S (Browser-Server) mode.
The C/S mode is characterized in that a server is responsible for data management, and a client is responsible for completing interaction tasks with a user. The client is connected with the server through the local area network, receives the request of the user, and makes the request to the server through the network to operate the database. The server receives the request of the client, submits the data to the client, and the client calculates the data and presents the result to the user. Illustratively, an application may be installed in the client, through which the client logs into the server.
The B/S mode is characterized in that the core part of the system function realization is centralized on a server, and the development, maintenance and use of the system are simplified. The client only needs to be provided with a browser such as Netscape Navigator or Internet Explorer, and the Server is provided with a database such as SQL Server, Oracle, MYSQL and the like. And the browser performs data interaction with the database through the Web Server.
The file transmission method provided by the embodiment of the application can be applied to the two architectures. To facilitate understanding of the present embodiment, a detailed description will be given of a structure of an electronic device that can be a client implementing device in a C/S mode or a B/S mode for executing the file transfer method disclosed in the embodiments of the present application.
Example one
As shown in fig. 1, is a block schematic diagram of an electronic device. The electronic device 100 may include a memory 111, a memory controller 112, a processor 113, a peripheral interface 114, an input-output unit 115, and a display unit 116. It will be understood by those of ordinary skill in the art that the structure shown in fig. 1 is merely exemplary and is not intended to limit the structure of the electronic device 100. For example, electronic device 100 may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.
The above-mentioned elements of the memory 111, the memory controller 112, the processor 113, the peripheral interface 114, the input/output unit 115 and the display unit 116 are electrically connected to each other directly or indirectly, so as to implement data transmission or interaction. For example, the components may be electrically connected to each other via one or more communication buses or signal lines. The processor 113 is used to execute the executable modules stored in the memory.
The Memory 111 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Read-Only Memory (EPROM), an electrically Erasable Read-Only Memory (EEPROM), and the like. The memory 111 is configured to store a computer program, and the processor 113 executes the computer program after receiving an execution instruction, and the method performed by the electronic device 100 defined by a process disclosed in any embodiment of the present application may be applied to the processor 113, or implemented by the processor 113.
The processor 113 may be an integrated circuit chip having signal processing capability. The Processor 113 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The peripheral interface 114 couples various input/output devices to the processor 113 and memory 111. In some embodiments, the peripheral interface 114, the processor 113, and the memory controller 112 may be implemented in a single chip. In other examples, they may be implemented separately from separate chips.
The input/output unit 115 is used to provide input data to the user. The input/output unit 115 may be, but is not limited to, a mouse, a keyboard, and the like.
The display unit 116 provides an interactive interface (e.g., a user operation interface) between the electronic device 100 and the user or is used for displaying image data to the user for reference. In this embodiment, the display unit may be a liquid crystal display or a touch display. In the case of a touch display, the display can be a capacitive touch screen or a resistive touch screen, which supports single-point and multi-point touch operations. The support of single-point and multi-point touch operations means that the touch display can sense touch operations simultaneously generated from one or more positions on the touch display, and the sensed touch operations are sent to the processor for calculation and processing.
The computer program described above may include: an operating system, a first application program, and a second application program. The operating system, such as LINUX, UNIX, WINDOWS, may include various software components and/or drivers for managing system tasks (e.g., memory management, storage device control, power management, etc.), and may communicate with various hardware or software components to provide an operating environment for other software components. The first application program may be a client or a browser. The second application program may be a WinSCP client or the like using a secure file transfer protocol. The first application program and the second application program run on the basis of the operating system, monitor the request from the network through the network service of the operating system, and complete corresponding data processing according to the request.
The electronic device 100 in this embodiment may be configured to perform each step in each method provided in this embodiment. The following describes the implementation process of the file transfer method in detail by several embodiments.
Example two
Please refer to fig. 2, which is a flowchart illustrating a file transmission method according to an embodiment of the present application. The specific process shown in fig. 2 will be described in detail below.
Illustratively, when a page on which a file transfer request is received is entered for the first time, a prompt message of whether to install the target plug-in is output.
For example, the page where the file transmission request is received may be an interface displayed after a browser inputs a certain web address, or may be an interface in a client, and if the interface includes the < Object > element of the target plug-in, the target plug-in may be called.
The prompt message may be output in a form of a small window different from the page where the file transfer request is received, or may be output embedded in the page where the file transfer request is received.
And after receiving a confirmation message input aiming at the prompt message, installing the target plug-in, and storing the executable file of the target plug-in a specified storage folder.
The designated storage file may be a system folder of the Windows operating system.
For example, the prompt message may be provided with a confirmation button, and after the confirmation button is clicked, the target plug-in is installed and registered. Alternatively, an executable file may be generated in the designated storage folder described above during the installation process. The executable file may be an OCX (Object Linking and Embedding (OLE) Control Extension) file, for example. The designated storage folder described above may be C: \ Windows \ System 32.
Illustratively, the properties of the object of the target plug-in described above may be defined by the following code:
illustratively, the first application may be a browser; or may be a client installed in the client.
Illustratively, the address access protocol of the browser may be defined as required, for example: and gv. Defining windows registry file, receiving parameters submitted by protocol access address, transmitting to target plug-in and executing writing into registry. Illustratively, the target plug-in described above may be a global processing script.
The second application may be invoked when accessed via a browser custom protocol URL (Uniform Resource Locator), which may be gv:// wincpsftp:// jiangxy:111111@10.0.35.253, for example.
Illustratively, the object of the target plug-in may be created after receiving the file transfer request described above.
Step 202 may include: creating a target object of the target plug-in based on the first application program; and calling a specified method in the target object to start the target plug-in.
Illustratively, the above-mentioned target plug-in may be an ActiveX plug-in.
Wherein the ActiveXObject object in JavaScript is a reference that enables and returns an Automation object.
Illustratively, creating the target object may use the following method:
newObj＝new ActiveXObject(servername.typename[,location])。
optionally, the ActiveXObject object syntax may include the following:
wherein newObj is a mandatory option to be assigned a variable name of ActiveXObject.
servername is a mandatory option that provides the name of the application for the object.
typename is a mandatory option, the type or class of object to be created.
location is an optional item, the name of the web server that created the object.
The Automation server provides at least one type of object, for example, a word processing application may provide an application object, a document object, and a toolbar object.
In use, calling method newobj. xxxfen () in the target object can then perform the action that the target plug-in needs to perform.
Step 203, starting the second application program through the target plug-in to process the file transmission request through the second application program.
The second application comprises a WinSCP client.
Step 203 may comprise: and starting the second application program through the specified method so as to process the file transmission request through the second application program.
The target plug-in can be developed by using c/c + +, and a JS object can be returned for page calling and processing by processing the interface in the target plug-in. Illustratively, an interface for calling the operating system is encapsulated in the OCX file of the executable file of the target plug-in, and the interface can be directly exposed to the page call for receiving the file transmission request through a method in the JS object.
For example, the login parameter of the second application may be transferred from the first application to the target plug-in and then from the target plug-in to the second application.
Alternatively, as shown in fig. 3, the step 203 may include the following steps.
The identity authentication information may include a user name, a user password, and the like.
Further, the access parameter required for the second application may be preset. For example, the access parameters may include file protocol, hostname, and the like.
According to the file transmission method, the second application program using the safe file transfer protocol is called to execute the file transmission request, compared with the JS component file uploading and the plug-in file uploading of the browser in the prior art, the JS component file uploading is used in the prior art, the HTTP protocol is used, the file transmission efficiency is low, the long-time waiting of the page is easily caused for the uploading of the large file, and the breakpoint continuous transmission is not supported due to the transmission failure. In addition, since the HTTP protocol is used for file plaintext transmission without any encryption process, there is a problem of security. According to the embodiment of the application, the efficiency, the stability and the safety of file uploading can be improved through uploading of the safe file transfer protocol.
EXAMPLE III
Based on the same application concept, a file transmission device corresponding to the file transmission method is further provided in the embodiment of the present application, and as the principle of solving the problem of the device in the embodiment of the present application is similar to the file transmission method in the embodiment of the present application, the implementation of the device can refer to the implementation of the method, and repeated details are not repeated.
Please refer to fig. 4, which is a schematic diagram of a functional module of a file transfer device according to an embodiment of the present application. Each module in the file transfer device in this embodiment is configured to execute each step in the above method embodiments. The file transfer device includes: a receiving module 301, a calling module 302 and a starting module 303; wherein the content of the first and second substances,
a receiving module 301, configured to receive a file transmission request through a first application;
a calling module 302, configured to call a target plug-in through the first application after receiving the file transmission request;
a starting module 303, configured to start the second application program through the target plug-in, and process the file transmission request through the second application program.
In a possible implementation, the file transfer device further includes:
an output module 304, configured to output a prompt message indicating whether to install the target plug-in when entering a page where the file transfer request is received for the first time;
the installation module 305 is configured to install the target plug-in after receiving the confirmation message input for the prompt message, and store the executable file of the target plug-in a designated storage folder.
In a possible implementation, the installation module 305 is further configured to:
and storing the executable file of the target plug-in a system folder of the Windows operating system.
In a possible implementation manner, the invoking module 302 is further configured to:
creating a target object of the target plug-in based on the first application program;
calling a specified method in the target object to start the target plug-in;
the step of processing the file transfer request by the second application includes: and starting the second application program through the specified method so as to process the file transmission request through the second application program.
In a possible implementation manner, the starting module 303 is further configured to:
acquiring user identity authentication information acquired by the target plug-in from the first application program through the second application program;
logging in a target server with the user identity authentication information through the second application program;
and uploading the transmission file corresponding to the file transmission request to the target server through the second application program.
In one possible embodiment, the first application is a browser.
In one possible embodiment, the second application is a WinSCP client.
In addition, an embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program performs the steps of the file transmission method in the foregoing method embodiment.
The computer program product of the file transmission method provided in the embodiment of the present application includes a computer-readable storage medium storing a program code, where instructions included in the program code may be used to execute the steps of the file transmission method in the above method embodiment, which may be specifically referred to in the above method embodiment, and are not described herein again.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules 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 or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including 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. It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (7)
1. A file transmission method is applied to electronic equipment, a first application program and a second application program are installed in the electronic equipment, and a protocol used by the second application program is a secure file transfer protocol, and the method comprises the following steps:
receiving a file transmission request through a first application program, wherein the first application program is a browser;
after receiving the file transmission request, calling a target plug-in through the first application program;
starting the second application program through the target plug-in so as to process the file transmission request through the second application program;
when the page where the file transmission request is received is entered for the first time, outputting a prompt message for judging whether the target plug-in is installed;
and after receiving a confirmation message input aiming at the prompt message, installing the target plug-in, and storing the executable file of the target plug-in a system folder of the Windows operating system.
2. The method of claim 1, wherein the step of invoking a target plug-in by the first application comprises:
creating a target object of the target plug-in based on the first application program;
calling a specified method in the target object to start the target plug-in;
the step of processing the file transfer request by the second application includes: and starting the second application program through the specified method so as to process the file transmission request through the second application program.
3. The method of claim 1, wherein the step of processing the file transfer request by the second application comprises:
acquiring user identity authentication information acquired by the target plug-in from the first application program through the second application program;
logging in a target server with the user identity authentication information through the second application program;
and uploading the transmission file corresponding to the file transmission request to the target server through the second application program.
4. The method of claim 3, wherein the second application is a WinSCP client.
5. A file transmission device is applied to electronic equipment, a first application program and a second application program are installed in the electronic equipment, a protocol used by the second application program is a secure file transfer protocol, and the device comprises:
the system comprises a receiving module, a file transmission module and a file transmission module, wherein the receiving module is used for receiving a file transmission request through a first application program, and the first application program is a browser;
the calling module is used for calling a target plug-in through the first application program after receiving the file transmission request;
the starting module is used for starting the second application program through the target plug-in and processing the file transmission request through the second application program;
the output module is used for outputting a prompt message whether the target plug-in is installed or not when the page where the file transmission request is received is entered for the first time;
and the installation module is used for installing the target plug-in after receiving the confirmation message input aiming at the prompt message and storing the executable file of the target plug-in a system folder of the Windows operating system.
6. An electronic device, comprising: a processor, a memory storing machine-readable instructions executable by the processor, the machine-readable instructions when executed by the processor performing the steps of the method of any of claims 1 to 4 when the electronic device is run.
7. A computer-readable storage medium, having stored thereon a computer program which, when being executed by a processor, is adapted to carry out the steps of the method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910840048.6A CN110557507B (en) | 2019-09-05 | 2019-09-05 | File transmission method and device, electronic equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910840048.6A CN110557507B (en) | 2019-09-05 | 2019-09-05 | File transmission method and device, electronic equipment and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110557507A CN110557507A (en) | 2019-12-10 |
| CN110557507B true CN110557507B (en) | 2021-06-11 |
Family
ID=68739285
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910840048.6A Active CN110557507B (en) | 2019-09-05 | 2019-09-05 | File transmission method and device, electronic equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110557507B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112379943A (en) * | 2020-11-17 | 2021-02-19 | 北京高途云集教育科技有限公司 | Plug-in application method and device of Electron application program and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101945136A (en) * | 2010-09-28 | 2011-01-12 | 北京伟库电子商务科技有限公司 | Data transmission method and system based on web application |
| CN106850805A (en) * | 2017-02-06 | 2017-06-13 | 网宿科技股份有限公司 | A kind of data transmission method and device |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070233688A1 (en) * | 2006-04-04 | 2007-10-04 | Karla Weekes Smolen | Online system for exchanging fraud investigation information |
| CN104572040A (en) * | 2013-10-15 | 2015-04-29 | 镇江雅迅软件有限责任公司 | On-line text processing method based on JSP and ActiveX control |
| CN104580298B (en) * | 2013-10-17 | 2018-05-08 | 北大方正集团有限公司 | File upload process method and device |
| CN103617055B (en) * | 2013-11-20 | 2017-12-08 | 北京奇虎科技有限公司 | A kind of method, apparatus and browser for starting application program in a browser |
| CN104079649B (en) * | 2014-06-27 | 2019-06-04 | 北京奇虎科技有限公司 | The method and browser being downloaded in a browser |
| CN104217173B (en) * | 2014-08-27 | 2018-04-17 | 武汉理工大学 | A kind of data and file encrypting method for browser |
| US10915655B2 (en) * | 2017-04-27 | 2021-02-09 | Dell Products L.P. | Browser drag and drop file upload encryption enforcement |
| CN109040252B (en) * | 2018-08-07 | 2022-04-12 | 平安科技（深圳）有限公司 | File transmission method, system, computer device and storage medium |
-
2019
- 2019-09-05 CN CN201910840048.6A patent/CN110557507B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101945136A (en) * | 2010-09-28 | 2011-01-12 | 北京伟库电子商务科技有限公司 | Data transmission method and system based on web application |
| CN106850805A (en) * | 2017-02-06 | 2017-06-13 | 网宿科技股份有限公司 | A kind of data transmission method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110557507A (en) | 2019-12-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11190513B2 (en) | Gateway enrollment for internet of things device management | |
| US20230370464A1 (en) | Systems and methods for controlling sign-on to web applications | |
| US9444899B2 (en) | Use of internet information services logging to collect user information in an asynchronous manner | |
| US20140173708A1 (en) | Cloud based password management | |
| US9213806B2 (en) | Managing and providing access to applications in an application-store module | |
| US20140019958A1 (en) | Enterprise portal mobile applications installs | |
| US10491621B2 (en) | Website security tracking across a network | |
| KR20170063724A (en) | Proxy servers within computer subnetworks | |
| EP3614643B1 (en) | Oauth2 saml token service | |
| US9137094B1 (en) | Method for setting DNS records | |
| US20150128222A1 (en) | Systems and methods for social media user verification | |
| CN103701779A (en) | Method and device for accessing website for second time and firewall equipment | |
| US10951682B2 (en) | Systems and methods for accessing multiple resources via one identifier | |
| US20200396276A1 (en) | Distributed historization system | |
| JP5400790B2 (en) | Method and system for entering data into a web page | |
| CN110557507B (en) | File transmission method and device, electronic equipment and computer readable storage medium | |
| US20150113628A1 (en) | Infrastructure support optimization | |
| AU2014412020B2 (en) | Techniques to transform network resource requests to zero rated network requests | |
| JP5753302B1 (en) | Program, method and system for warning access to web page | |
| CN113852621B (en) | License information determining method and device based on Jenkins server and storage medium | |
| US9424552B2 (en) | Managing website registrations | |
| US9031973B2 (en) | Management platform for displaying benefit plan data to permitted entities | |
| US10659560B2 (en) | Mobile device display preference | |
| CN107204970B (en) | Single sign-on method and related device | |
| US20180329806A1 (en) | Developer experience for application programming interfaces with variability |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20211021 Address after: 100089 building 36, courtyard 8, Dongbeiwang West Road, Haidian District, Beijing Patentee after: Dawning Information Industry (Beijing) Co.,Ltd. Patentee after: ZHONGKE SUGON INFORMATION INDUSTRY CHENGDU Co.,Ltd. Address before: Building 36, yard 8, Dongbei Wangxi Road, Haidian District, Beijing Patentee before: Dawning Information Industry (Beijing) Co.,Ltd. |