CN105450449A - File operation methods and devices - Google Patents
File operation methods and devices Download PDFInfo
- Publication number
- CN105450449A CN105450449A CN201510864639.9A CN201510864639A CN105450449A CN 105450449 A CN105450449 A CN 105450449A CN 201510864639 A CN201510864639 A CN 201510864639A CN 105450449 A CN105450449 A CN 105450449A
- Authority
- CN
- China
- Prior art keywords
- journalizing
- journal file
- file
- client
- operational order
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
-
- 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
Abstract
The invention discloses file operation methods and devices. An embodiment of the method comprises the steps of receiving an operation request for a log file sent from the terminal, wherein the operation request comprises an operation identifier of a preset log operation for the log file and a client identifier; and generating an operation instruction including the operation identifier; and sending the operation instruction to a client corresponding to the client identifier, so as to enable the client to respond to the operation instruction to execute the log operation that is corresponding to the operation identifier and is of the type to which the log file belongs. According to the method, unified management and operation for the log file are realized; an independent interface is not configured for the client, corresponding configuration files are not arranged at both the client and the terminal, so that coupling between the terminal and the client in log operation is reduced, and the system stability is improved.
Description
Technical field
The application relates to computer realm, is specifically related to application, particularly relates to file operation method and device.
Background technology
Journal file is the file recorded the operation that client performs, to recover operation when system jam.At present, when operating journal file, the mode usually adopted is: operated journal file by specific journalizing interface.Such as, when needing the output level changing journal file, need to arrange specifically for changing the operation-interface of the output level of journal file and adding correspondingly configuration file in client.
But, when adopting aforesaid way to operate journal file, on the one hand, all needing to arrange specific journalizing interface and configuration file for each client, increasing system redundancy.On the other hand, specific journalizing interface is set and configuration file is only applicable to single main frame, the unified operation to journal file cannot be realized, reduce the stability of system.
Summary of the invention
This application provides file operation method and device, for solving the technical problem that above-mentioned background technology part exists.
First aspect, this application provides file operation method, the method comprises: the operation requests to journal file that receiving terminal sends, operation requests comprises operation mark to the default journalizing that journal file carries out and client identification, journal file is the file for recording the operation performed on the client, wherein, each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file; Generate the operational order comprising operation mark; Operational order is sent to the client that client identification is corresponding, to make client end response in operational order, executable operations identifies the journalizing of corresponding, belonging to journal file type.
Second aspect, this application provides file operation method, the method comprises: the operational order that reception server sends, operational order comprises the operation mark to the default journalizing that journal file carries out, wherein, each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file; Determine the type of journal file; Executable operations identifies the journalizing of type that is corresponding, that determine.
The third aspect, this application provides file operation method, the method comprises: the operating parameter to journal file receiving input, operating parameter comprises: client identification and the operation mark to the default journalizing that journal file carries out, journal file is the file for recording the operation performed on the client, wherein, each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file; Generate the operation requests comprising client identification and operation mark; Operation requests is sent to server, to make server be sent to client corresponding to client identification based on after the instruction of operation requests generating run, by client executing operation mark corresponding, the journalizing of type belonging to journal file.
Fourth aspect, this application provides file operation device, this device comprises: operation requests receiving element, be configured for the operation requests to journal file that receiving terminal sends, operation requests comprises operation mark to the default journalizing that journal file carries out and client identification, journal file is the file for recording the operation performed on the client, and wherein, each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file; Operational order generation unit, is configured for the operational order generating and comprise operation mark; Operational order transmitting element, is configured for and operational order is sent to client corresponding to client identification, and to make client end response in operational order, executable operations identifies the journalizing of corresponding, belonging to journal file type.
5th aspect, this application provides file operation device, this device comprises: operational order receiving element, be configured for the operational order that reception server sends, operational order comprises the operation mark to the default journalizing that journal file carries out, wherein, each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file; Determining unit, is configured for the type determining journal file; Performance element, the journalizing of type that be configured for executable operations mark correspondence, that determine.
6th aspect, this application provides file operation device, this device comprises: operating parameter receiving element, be configured for the operating parameter to journal file receiving input, operating parameter comprises: client identification and the operation mark to the default journalizing that journal file carries out, journal file is the file for recording the operation performed on the client, and wherein, each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file; Operation requests generation unit, is configured for the operation requests generating and comprise client identification and operation mark; Operation requests transmitting element, be configured for and operation requests is sent to server, to make server be sent to client corresponding to client identification based on after the instruction of operation requests generating run, by client executing operation mark corresponding, the journalizing of type belonging to journal file.
The file operation method that the application provides and device, the operation requests to journal file sent by receiving terminal, operation requests comprises operation mark to the default journalizing that journal file carries out and client identification; Generate the operational order comprising operation mark; Operational order is sent to the client that client identification is corresponding, to make client end response in operational order, executable operations identifies the journalizing of corresponding, belonging to journal file type.Achieve the unified management to journal file and operation, without the need to arranging independently interface and simultaneously arrange corresponding configuration file in client and terminal for client, thus decrease being coupled in journalizing process between terminal with client, the stability of elevator system.
Accompanying drawing explanation
By reading the detailed description done non-limiting example done with reference to the following drawings, the other features, objects and advantages of the application will become more obvious:
Fig. 1 is the exemplary system architecture figure that the application can be applied to wherein;
Fig. 2 shows the flow chart of an embodiment of the file operation method according to the application;
Fig. 3 shows the flow chart of another embodiment of the file operation method according to the application;
Fig. 4 shows the flow chart of another embodiment of the file operation method according to the application;
Fig. 5 shows the structural representation of an embodiment of the file operation device according to the application;
Fig. 6 shows the structural representation of another embodiment of the file operation device according to the application;
Fig. 7 shows the structural representation of another embodiment of the file operation device according to the application;
Fig. 8 is the structural representation of the computer system be suitable for for the terminal equipment or server realizing the embodiment of the present application.
Embodiment
Below in conjunction with drawings and Examples, the application is described in further detail.Be understandable that, specific embodiment described herein is only for explaining related invention, but not the restriction to this invention.It also should be noted that, for convenience of description, in accompanying drawing, illustrate only the part relevant to Invention.
It should be noted that, when not conflicting, the embodiment in the application and the feature in embodiment can combine mutually.Below with reference to the accompanying drawings and describe the application in detail in conjunction with the embodiments.
Fig. 1 shows the exemplary system architecture 100 can applying the file operation method of the application or the embodiment of device.
As shown in Figure 1, system architecture 100 can comprise terminal 101, server 102, client 103.Network 104 in order to provide the medium of transmission link between terminal equipment 101 and server 102.Network 104 can comprise various wired, wireless transmission link.Network 105 in order to provide the medium of transmission link between server 102 and client 103.Network 105 can comprise wired transmission links, such as fiber optic cables.
Client 103 can for providing the server of online service.Server 102 can provide data management service to the online service that multiple client 103 is run, and such as, changes the parameter of online service.Therefore, relative to the client 103 of data management service accepting server 102, also the one end at server 102 place can be referred to as service end.Terminal 101 can receive the operational order of user's input, then operational order is sent to server 102, to manage the online service that multiple client 103 is run.
Please refer to Fig. 2, it illustrates the flow process 200 of an embodiment of the file operation method according to the application.It should be noted that, the file operation method that the embodiment of the present application provides generally is performed by the server 102 in Fig. 1, and correspondingly, file operation device is generally positioned in server 102.The method comprises the following steps:
Step 201, the operation requests to journal file that receiving terminal sends.
In the present embodiment, the electronic equipment (server 102 such as shown in Fig. 1) that file operation method runs thereon can utilize the operation requests of its terminal of carrying out journalizing (terminal 101 such as shown in Fig. 1) reception to journal file by wired connection mode or radio connection from user.
In the present embodiment, operation requests comprises operation mark to the default journalizing that journal file carries out and client identification, and journal file is the file for recording the operation performed on the client.In the present embodiment, each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file.
In the present embodiment, the type of journal file can be log4j journal file, slf4j journal file.In the present embodiment, default journalizing can be applicable to for predefined the journalizing journal file of multiple type being carried out to unified operation.Correspondingly, the operation mark presetting journalizing can correspond to multiple journalizing performed dissimilar journal file in advance.Be example for the output level alter operation of output level changing journal file, the operation mark presetting output level alter operation can the output level alter operation of each self-supporting of journal file of corresponding multiple type in advance.
Step 202, generates the operational order comprising operation mark.
In the present embodiment, after the operation requests to journal file that receiving terminal sends, the operational order comprising operation mark can be generated.
Step 203, is sent to the client that client identification is corresponding by operational order.
In the present embodiment, after generation comprises the operational order of operation mark, operational order can be sent to client corresponding to client identification, make client can in response to operational order, to client presently used journal file executable operations mark corresponding, the journalizing of type belonging to this journal file.For the default output level alter operation that default journalizing is the output level for changing journal file, when after client transmit operation instruction, client can be made by the operation mark of default output level alter operation and the corresponding relation to the output level alter operation that dissimilar journal file performs, find out corresponding with operation mark, the output level alter operation of the type belonging to the journal file of current use, then, perform this output level alter operation, thus, the output level of the journal file of the current use of client is changed.
The following describes in the present embodiment in the mode of operation of journal file and prior art to the difference of the mode of operation of journal file: on the one hand, in the prior art, when the journal file of terminal to client operates, need to arrange specific operation-interface in client and add correspondingly configuration file in terminal and client simultaneously.And in the present embodiment, by carrying out unified operation to dissimilar log system, decrease being coupled between terminal with client, alleviate system load.On the other hand, in the prior art, specific journalizing interface is set and configuration file is only applicable to single client, the unified operation to journal file cannot be realized, when the journalizing of client breaks down, the fault of the journalizing of terminal can be caused simultaneously, reduce the stability of system.And in the present embodiment, achieving in the operating process of journal file, terminal is separated with client, makes the operation of terminal can not by the impact of the operation of client, the stability of further elevator system.
Please refer to Fig. 3, it illustrates the flow process 300 of another embodiment of the file operation method according to the application.It should be noted that, the file operation method that the embodiment of the present application provides generally is performed by the client 103 in Fig. 1, and correspondingly, file operation device is generally positioned in client 103.The method comprises the following steps:
Step 301, the operational order that reception server sends.
In the present embodiment, the electronic equipment (client 103 such as shown in Fig. 1) that file operation method runs thereon can receive operational order by wired connection mode (such as optical fiber) from providing the electronic equipment (server 102 such as shown in Fig. 1) of data management service.In the present embodiment, operational order comprises the operation mark to the default journalizing that journal file carries out, and each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file.
In some optional implementations of the present embodiment, default journalizing comprises: for changing the output level alter operation of the output level of journal file.In the present embodiment, the operation mark of default output level alter operation and multiple corresponding relation to the output level alter operation that dissimilar journal file performs can be set up in advance.Such as, the corresponding relation presetting the output level alter operation that the operation mark of output level alter operation and log4j journal file, slf4j journal file are supported is set up in advance.
In some optional implementations of the present embodiment, the operational order that reception server sends comprises: utilize journalizing interface operational order, before the operational order that reception server sends, being identified on server of journalizing interface is registered.
In the present embodiment, journalizing interface (such as reading the query interface of journal file) can be pre-created.Then, the default mark of journalizing and the corresponding relation to the journalizing that dissimilar journal file performs can be defined in journalizing interface.For the default output level alter operation that default journalizing is the output level for changing journal file, the operation mark and multiple corresponding relation to the output level alter operation that dissimilar journal file performs of presetting output level alter operation can be defined in journalizing interface, such as, the corresponding relation presetting the output level alter operation that the operation mark of output level alter operation and log4j journal file, slf4j journal file are supported is set up in advance.Thus, when utilizing journalizing interface operational order, first can parse the operation mark of default journalizing from operational order, then, determining the journalizing of this mark correspondence.In the present embodiment, being in advance identified on server of journalizing interface can be registered, thus make when server receives operational order, operational order can be sent to chartered journalizing interface.
In the present embodiment, journalizing interface and the Bean object in Spring framework all can be utilized to define to the journalizing that dissimilar journal file performs, i.e. daily record operation-interface and the source code respectively corresponding Bean object to the operation of dissimilar journal file.Then, the life cycle of the Spring container in Spring framework to above-mentioned Bean object can be utilized to manage, such as, start Bean object and instantiation Bean object.
Step 302, determines the type of journal file.
In the present embodiment, after the operational order to journal file receiving server transmission, the type of presently used journal file can be determined further.
Step 303, executable operations identifies the journalizing of type that is corresponding, that determine.
In the present embodiment, can based on the operation mark of default journalizing and the corresponding relation to the journalizing that dissimilar daily record performs, determination operation identifies the journalizing of type that is corresponding, that determine, then performs this journalizing.With the type of presently used journal file for Log4j journal file, performing output level alter operation to Log4j journal file is example, can based on the operation mark of default output level alter operation and multiple corresponding relation to the output level alter operation that dissimilar journal file performs, find out the output level alter operation that Log4j journal file is performed, perform this output level alter operation, thus the output level of Log4j journal file is changed.
In some optional implementations of the present embodiment, also comprise: the download address obtaining the executable file bag generated after journalizing interface and multiple source code to the journalizing that dissimilar journal file performs being packed; Executable file bag is downloaded from download address, and based on the source code in executable file bag, instantiation is carried out to journalizing interface and multiple journalizing to the execution of dissimilar journal file, to make journalizing interface and multiple journalizing load operating performed dissimilar journal file.
In the present embodiment, can increase in POM (ProjectObjectModel) file in advance journalizing interface and multiple source code of journalizing performed dissimilar daily record are packed after the download address of JAR bag (executable file bag) that generates.Then, JAR bag can be obtained from this download address.After installation JAR bag, can utilize Spring container that the journalizing interface in source code and multiple Bean object corresponding to the journalizing of dissimilar journal file execution are carried out instantiation, to make journalizing interface and multiple journalizing load operating performed dissimilar journal file, thus the journalizing interface of load operating, the journalizing to the execution of dissimilar journal file can be utilized, find out operation mark corresponding, the journalizing of the type of presently used journal file, then perform this journalizing.
In the present embodiment, when carrying out unified operation to dissimilar journal file, only need to obtain in advance the JAR bag comprising journalizing interface and multiple source code to the journalizing that dissimilar daily record performs, JAR bag is installed, can by journalizing interface and multiple journalizing load operating performed dissimilar daily record, thus utilize the journalizing interface of load operating, the operation of dissimilar journal file is come executable operations mark corresponding, the journalizing of type determined, thus realize zero cost access.
Please refer to Fig. 4, it illustrates the flow process 400 of another embodiment of the file operation method according to the application.It should be noted that, the file operation method that the embodiment of the present application provides generally is performed by the terminal 101 in Fig. 1, and correspondingly, file operation device is generally positioned in terminal 101.The method comprises the following steps:
Step 401, receives the operating parameter to journal file of input.
In the present embodiment, the operating parameter to journal file of input can be received by the file operation method electronic equipment (terminal 101 such as shown in Fig. 1) run thereon.Such as, receive by control desk the operating parameter to journal file that user (such as O&M engineer) inputs.Operating parameter comprises: client identification and the operation mark to the default journalizing that journal file carries out, journal file is the file for recording the operation performed on the client, wherein, each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file.
In the present embodiment, can verify the authority of user in advance.Such as, when user revises the output level of journal file, can first verify the authority of user, after passing through Authority Verification, can to client transmit operation request.
Step 402, generates the operation requests comprising client identification and operation mark.
In the present embodiment, after the operating parameter to journal file receiving input, the operation requests comprising client identification and operation mark can be generated.
Step 403, is sent to server by operation requests.
In the present embodiment, after generation comprises the operation requests of client identification and operation mark, operation requests can be sent to server, to make server be sent to client corresponding to client identification based on after the instruction of operation requests generating run, by client executing operation mark corresponding, the journalizing of type belonging to journal file.
With further reference to Fig. 5, this application provides an a kind of embodiment of file operation device, this device embodiment is corresponding with the embodiment of the method shown in Fig. 2, and this device specifically can be applied in various electronic equipment.
As shown in Figure 5, the file operation device 500 of the present embodiment comprises: operation requests receiving element 501, operational order generation unit 502, operational order transmitting element 503.Wherein, operation requests receiving element 501 is configured for the operation requests to journal file that receiving terminal sends, operation requests comprises operation mark to the default journalizing that journal file carries out and client identification, journal file is the file for recording the operation performed on the client, wherein, each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file; Operational order generation unit 502 is configured for the operational order generating and comprise operation mark; Operational order transmitting element 503 is configured for and operational order is sent to client corresponding to client identification, and to make client end response in operational order, executable operations identifies the journalizing of corresponding, belonging to journal file type.
In the present embodiment, operation requests receiving element 501 can carry out the operation requests of terminal reception to journal file of journalizing by wired connection mode or radio connection from user.Default journalizing can be applicable to for predefined the journalizing daily record of multiple type being carried out to unified operation.Correspondingly, the operation mark presetting journalizing can correspond to multiple journalizing performed dissimilar daily record in advance.
In the present embodiment, after the operation requests to journal file that operational order generation unit 502 can send at receiving terminal, the operational order comprising operation mark can be generated.
In the present embodiment, operational order can be sent to client corresponding to client identification by operational order transmitting element 503, make client can in response to operational order, to client presently used journal file executable operations mark corresponding, the journalizing of type belonging to journal file.
It will be understood by those skilled in the art that above-mentioned file operation device 500 also comprises some other known features, such as processor, memories etc., in order to unnecessarily fuzzy embodiment of the present disclosure, these known structures are not shown in Figure 5.
With further reference to Fig. 6, this application provides another embodiment of a kind of file operation device, this device embodiment is corresponding with the embodiment of the method shown in Fig. 3, and this device specifically can be applied in various electronic equipment.
As shown in Figure 6, the file operation device 600 of the present embodiment comprises: operational order receiving element 601, determining unit 602, performance element 603.Wherein, operational order receiving element 601 is configured for the operational order that reception server sends, operational order comprises the operation mark to the default journalizing that journal file carries out, and wherein, each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file; Determining unit 602 is configured for the type determining journal file; The journalizing of type that performance element 603 is configured for executable operations mark correspondence, that determine.
In the present embodiment, operational order receiving element 601 can receive operational order by wired connection mode from the server for clients providing data management service.
In the present embodiment, determining unit 602 after the operational order to journal file receiving server transmission, can determine the type of presently used journal file further.
In the present embodiment, performance element 603 can based on the operation mark of default journalizing and the corresponding relation to the journalizing that dissimilar journal file performs, determination operation identifies the journalizing of type that is corresponding, presently used journal file, then, performs this journalizing.
In some optional implementations of the present embodiment, default journalizing comprises: for changing the output level alter operation of the output level of journal file.
In some optional implementations of the present embodiment, operational order receiving element 601 comprises: operation-interface subelement (not shown), is configured for and utilizes journalizing interface operational order.
In some optional implementations of the present embodiment, device 600 also comprises: registering unit (not shown), before being configured for the operational order sent at reception server, being identified on server of journalizing interface is registered.
In some optional implementations of the present embodiment, device 600 also comprises: download address acquiring unit (not shown), is configured for the download address of the executable file bag generated after journalizing interface and multiple source code to the journalizing that dissimilar journal file performs are packed by acquisition; File bag processing unit (not shown), be configured for and download executable file bag from download address, and based on the source code in executable file bag, instantiation is carried out to journalizing interface and multiple journalizing to the execution of dissimilar journal file, to make journalizing interface and multiple journalizing load operating performed dissimilar journal file.
It will be understood by those skilled in the art that above-mentioned file operation device 600 also comprises some other known features, such as processor, memories etc., in order to unnecessarily fuzzy embodiment of the present disclosure, these known structures are not shown in figure 6.
With further reference to Fig. 7, this application provides another embodiment of a kind of file operation device, this device embodiment is corresponding with the embodiment of the method shown in Fig. 4, and this device specifically can be applied in various electronic equipment.
As shown in Figure 7, the file operation device 700 of the present embodiment comprises: operating parameter receiving element 701, operation requests generation unit 702, operation requests transmitting element 703.Wherein, operating parameter receiving element 701 is configured for the operating parameter to journal file receiving input, operating parameter comprises: client identification and the operation mark to the default journalizing that journal file carries out, journal file is the file for recording the operation performed on the client, wherein, each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file; Operation requests generation unit 702 is configured for the operation requests generating and comprise client identification and operation mark; Operation requests transmitting element 703 is configured for and operation requests is sent to server, to make server be sent to client corresponding to client identification based on after the instruction of operation requests generating run, by client executing operation mark corresponding, the journalizing of type belonging to journal file.
In the present embodiment, operating parameter receiving element 701 can receive the operating parameter to journal file of user's input by control desk.
In the present embodiment, operation requests generation unit 702 after the operating parameter to journal file receiving input, can generate the operation requests comprising client identification and operation mark.
In the present embodiment, operation requests transmitting element 703 can after generation comprises the operation requests of client identification and operation mark, operation requests is sent to server, to make server be sent to client corresponding to client identification based on after the instruction of operation requests generating run, by client executing operation mark corresponding, the journalizing of type belonging to journal file.
It will be understood by those skilled in the art that above-mentioned file operation device 700 also comprises some other known features, such as processor, memories etc., in order to unnecessarily fuzzy embodiment of the present disclosure, these known structures are not shown in the figure 7.
Fig. 8 shows the structural representation of the computer system be suitable for for the terminal equipment or server realizing the embodiment of the present application.
As shown in Figure 8, computer system 800 comprises CPU (CPU) 801, and it or can be loaded into the program random access storage device (RAM) 803 from storage area 808 and perform various suitable action and process according to the program be stored in read-only memory (ROM) 802.In RAM803, also store system 800 and operate required various program and data.CPU801, ROM802 and RAM803 are connected with each other by bus 804.I/O (I/O) interface 805 is also connected to bus 804.
I/O interface 805 is connected to: the importation 806 comprising keyboard, mouse etc. with lower component; Comprise the output 807 of such as cathode ray tube (CRT), liquid crystal display (LCD) etc. and loud speaker etc.; Comprise the storage area 808 of hard disk etc.; And comprise the communications portion 809 of network interface unit of such as LAN card, modulator-demodulator etc.Communications portion 809 is via the network executive communication process of such as internet.Driver 810 is also connected to I/O interface 805 as required.Detachable media 811, such as disk, CD, magneto optical disk, semiconductor memory etc., be arranged on driver 810 as required, so that the computer program read from it is mounted into storage area 808 as required.
Especially, according to embodiment of the present disclosure, the process that reference flow sheet describes above may be implemented as computer software programs.Such as, embodiment of the present disclosure comprises a kind of computer program, and it comprises the computer program visibly comprised on a machine-readable medium, and described computer program comprises the program code for the method shown in flowchart.In such embodiments, this computer program can be downloaded and installed from network by communications portion 809, and/or is mounted from detachable media 811.
Flow chart in accompanying drawing and block diagram, illustrate according to the architectural framework in the cards of the system of the various embodiment of the application, method and computer program product, function and operation.In this, each square frame in flow chart or block diagram can represent a part for module, program segment or a code, and a part for described module, program segment or code comprises one or more executable instruction for realizing the logic function specified.Also it should be noted that at some as in the realization of replacing, the function marked in square frame also can be different from occurring in sequence of marking in accompanying drawing.Such as, in fact the square frame that two adjoining lands represent can perform substantially concurrently, and they also can perform by contrary order sometimes, and this determines according to involved function.Also it should be noted that, the combination of the square frame in each square frame in block diagram and/or flow chart and block diagram and/or flow chart, can realize by the special hardware based system of the function put rules into practice or operation, or can realize with the combination of specialized hardware and computer instruction.
As another aspect, present invention also provides a kind of non-volatile computer storage medium, this non-volatile computer storage medium can be the non-volatile computer storage medium comprised in device described in above-described embodiment; Also can be individualism, be unkitted the non-volatile computer storage medium allocated in terminal.Above-mentioned non-volatile computer storage medium stores one or more program, when one or more program described is performed by an equipment, make described equipment: the operation requests to journal file that receiving terminal sends, described operation requests comprises operation mark to the default journalizing that journal file carries out and client identification, described journal file is the file for recording the operation performed on the client, wherein, each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file; Generate the operational order comprising described operation mark; Described operational order is sent to client corresponding to described client identification, to make described client end response in described operational order, perform described operation mark corresponding, the journalizing of type belonging to described journal file.
More than describe and be only the preferred embodiment of the application and the explanation to institute's application technology principle.Those skilled in the art are to be understood that, invention scope involved in the application, be not limited to the technical scheme of the particular combination of above-mentioned technical characteristic, also should be encompassed in when not departing from described inventive concept, other technical scheme of being carried out combination in any by above-mentioned technical characteristic or its equivalent feature and being formed simultaneously.The technical characteristic that such as, disclosed in above-mentioned feature and the application (but being not limited to) has similar functions is replaced mutually and the technical scheme formed.
Claims (14)
1. a file operation method, is characterized in that, described method comprises:
The operation requests to journal file that receiving terminal sends, described operation requests comprises operation mark to the default journalizing that journal file carries out and client identification, described journal file is the file for recording the operation performed on the client, wherein, each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file;
Generate the operational order comprising described operation mark;
Described operational order is sent to client corresponding to described client identification, to make described client end response in described operational order, perform described operation mark corresponding, the journalizing of type belonging to described journal file.
2. a file operation method, is characterized in that, described method comprises:
The operational order that reception server sends, described operational order comprises the operation mark to the default journalizing that journal file carries out, and wherein, each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file;
Determine the type of described journal file;
Perform described operation mark corresponding, the journalizing of type determined.
3. method according to claim 2, is characterized in that, described default journalizing comprises: for changing the output level alter operation of the output level of journal file.
4. method according to claim 3, is characterized in that, the operational order that described reception server sends comprises: utilize operational order described in journalizing interface.
5. method according to claim 4, is characterized in that, before the operational order that reception server sends, described method also comprises:
Being identified on described server of described journalizing interface is registered.
6. method according to claim 5, is characterized in that, described method also comprises:
Obtain the download address of the executable file bag generated after described journalizing interface and multiple source code to the journalizing that dissimilar journal file performs being packed;
Described executable file bag is downloaded from described download address, and based on the described source code in executable file bag, instantiation is carried out to journalizing interface and multiple journalizing to the execution of dissimilar journal file, to make journalizing interface and multiple journalizing load operating performed dissimilar journal file.
7. a file operation method, is characterized in that, described method comprises:
Receive the operating parameter to journal file of input, described operating parameter comprises: client identification and the operation mark to the default journalizing that journal file carries out, described journal file is the file for recording the operation performed on the client, wherein, each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file;
Generate the operation requests comprising described client identification and operation mark;
Described operation requests is sent to server, to make server be sent to client corresponding to client identification based on after the instruction of described operation requests generating run, by operation mark described in described client executing corresponding, the journalizing of type belonging to described journal file.
8. a file operation device, is characterized in that, described device comprises:
Operation requests receiving element, be configured for the operation requests to journal file that receiving terminal sends, described operation requests comprises operation mark to the default journalizing that journal file carries out and client identification, described journal file is the file for recording the operation performed on the client, wherein, each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file;
Operational order generation unit, is configured for the operational order generating and comprise described operation mark;
Operational order transmitting element, be configured for and described operational order is sent to client corresponding to described client identification, to make described client end response in described operational order, perform described operation mark corresponding, the journalizing of type belonging to described journal file.
9. a file operation device, is characterized in that, described device comprises:
Operational order receiving element, be configured for the operational order that reception server sends, described operational order comprises the operation mark to the default journalizing that journal file carries out, and wherein, each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file;
Determining unit, is configured for the type determining described journal file;
Performance element, be configured for perform described operation mark corresponding, the journalizing of type determined.
10. device according to claim 9, is characterized in that, described default journalizing comprises: for changing the output level alter operation of the output level of journal file.
11. devices according to claim 10, is characterized in that, described operational order receiving element comprises:
Operation-interface subelement, is configured for and utilizes operational order described in journalizing interface.
12. devices according to claim 11, is characterized in that, described device also comprises:
Registering unit, before being configured for the operational order sent at reception server, registers being identified on described server of described journalizing interface.
13. devices according to claim 12, is characterized in that, described device also comprises:
Download address acquiring unit, is configured for the download address of the executable file bag generated after described journalizing interface and multiple source code to the journalizing that dissimilar journal file performs are packed by acquisition;
File bag processing unit, be configured for and download described executable file bag from described download address, and based on the described source code in executable file bag, instantiation is carried out to journalizing interface and multiple journalizing to the execution of dissimilar journal file, to make journalizing interface and multiple journalizing load operating performed dissimilar journal file.
14. 1 kinds of file operation device, is characterized in that, described device comprises:
Operating parameter receiving element, be configured for the operating parameter to journal file receiving input, described operating parameter comprises: client identification and the operation mark to the default journalizing that journal file carries out, described journal file is the file for recording the operation performed on the client, wherein, each operation mark is preset as corresponding multiple journalizing performed dissimilar journal file;
Operation requests generation unit, is configured for the operation requests generating and comprise described client identification and operation mark;
Operation requests transmitting element, be configured for and described operation requests is sent to server, to make server be sent to client corresponding to client identification based on after the instruction of described operation requests generating run, by operation mark described in described client executing corresponding, the journalizing of type belonging to described journal file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510864639.9A CN105450449A (en) | 2015-12-01 | 2015-12-01 | File operation methods and devices |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510864639.9A CN105450449A (en) | 2015-12-01 | 2015-12-01 | File operation methods and devices |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105450449A true CN105450449A (en) | 2016-03-30 |
Family
ID=55560255
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510864639.9A Pending CN105450449A (en) | 2015-12-01 | 2015-12-01 | File operation methods and devices |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105450449A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106776064A (en) * | 2016-11-29 | 2017-05-31 | 北京元心科技有限公司 | Method and device for managing logs in multiple systems |
| CN107329880A (en) * | 2017-05-26 | 2017-11-07 | 武汉斗鱼网络科技有限公司 | The method and system of dynamic access daily record example in a kind of java environment |
| CN110489390A (en) * | 2018-05-09 | 2019-11-22 | 杭州海康威视数字技术股份有限公司 | Log recording method and device and logger generation method and device |
| CN110928850A (en) * | 2018-08-29 | 2020-03-27 | 北京京东尚科信息技术有限公司 | Traffic statistic method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101183983A (en) * | 2007-12-12 | 2008-05-21 | 华为技术有限公司 | Operation log information recording method, device and system |
| CN102404140A (en) * | 2011-10-26 | 2012-04-04 | 深圳第七大道科技有限公司 | Control method, device and system of distributed servers |
| CN103645982A (en) * | 2013-11-29 | 2014-03-19 | 北京奇虎科技有限公司 | Log processing method and client |
| CN104486346A (en) * | 2014-12-19 | 2015-04-01 | 北京奇艺世纪科技有限公司 | Stepping stone system |
-
2015
- 2015-12-01 CN CN201510864639.9A patent/CN105450449A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101183983A (en) * | 2007-12-12 | 2008-05-21 | 华为技术有限公司 | Operation log information recording method, device and system |
| CN102404140A (en) * | 2011-10-26 | 2012-04-04 | 深圳第七大道科技有限公司 | Control method, device and system of distributed servers |
| CN103645982A (en) * | 2013-11-29 | 2014-03-19 | 北京奇虎科技有限公司 | Log processing method and client |
| CN104486346A (en) * | 2014-12-19 | 2015-04-01 | 北京奇艺世纪科技有限公司 | Stepping stone system |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106776064A (en) * | 2016-11-29 | 2017-05-31 | 北京元心科技有限公司 | Method and device for managing logs in multiple systems |
| CN106776064B (en) * | 2016-11-29 | 2020-06-09 | 北京元心科技有限公司 | Method and device for managing logs in multiple systems |
| CN107329880A (en) * | 2017-05-26 | 2017-11-07 | 武汉斗鱼网络科技有限公司 | The method and system of dynamic access daily record example in a kind of java environment |
| CN110489390A (en) * | 2018-05-09 | 2019-11-22 | 杭州海康威视数字技术股份有限公司 | Log recording method and device and logger generation method and device |
| CN110489390B (en) * | 2018-05-09 | 2022-05-03 | 杭州海康威视数字技术股份有限公司 | Log recording method and device and log recorder generating method and device |
| CN110928850A (en) * | 2018-08-29 | 2020-03-27 | 北京京东尚科信息技术有限公司 | Traffic statistic method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10225145B2 (en) | Method and device for updating client | |
| US10430172B2 (en) | Re-configuration in cloud computing environments | |
| CN101572598B (en) | Method and device for reliable rapid integration | |
| CN104067276B (en) | Client-side minimum is downloaded and the page navigation feature of simulation | |
| CN105337787A (en) | Multi-server monitoring method, device and system | |
| US7937432B2 (en) | State transition management according to a workflow management policy | |
| US20090064130A1 (en) | Updating a workflow when a user reaches an impasse in the workflow | |
| CN103209223A (en) | Distributed application conversation information sharing method and system and application server | |
| CN102197364A (en) | Systems and methods for managing printer settings in a networked computing environment | |
| US9001364B2 (en) | Management system, image forming apparatus, management system control method, and image forming apparatus control method for migration of setting values of an application that operates in the image forimng apparatus | |
| CN109547524B (en) | User behavior storage method, device, equipment and storage medium based on Internet of things | |
| CN105450449A (en) | File operation methods and devices | |
| CN110011875B (en) | Dial testing method, device, equipment and computer readable storage medium | |
| CN104769572A (en) | Updating a front end client | |
| CN104866290A (en) | Method and device for data transmission | |
| CN109669787B (en) | Data transmission method and device, storage medium and electronic equipment | |
| US11212658B2 (en) | Method for providing near filed communication device information for user and system therefor | |
| CN109104368B (en) | Connection request method, device, server and computer readable storage medium | |
| US9537940B2 (en) | Exchange of information between processing servers | |
| KR101977401B1 (en) | Commucation device providing dynamic modbus protocol mapping | |
| CN103581040A (en) | Server distributing device and server distributing method | |
| JP5268589B2 (en) | Information processing apparatus and information processing apparatus operating method | |
| JP2019192190A (en) | Cloud scraping system and method using pre-scraped big data, and computer program therefor | |
| US8984124B2 (en) | System and method for adaptive data monitoring | |
| US9690636B2 (en) | Apparatus and method of data communication between web applications |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160330 |