CN102117286B - Registry system and operation method thereof - Google Patents
Registry system and operation method thereof Download PDFInfo
- Publication number
- CN102117286B CN102117286B CN200910244153.XA CN200910244153A CN102117286B CN 102117286 B CN102117286 B CN 102117286B CN 200910244153 A CN200910244153 A CN 200910244153A CN 102117286 B CN102117286 B CN 102117286B
- Authority
- CN
- China
- Prior art keywords
- registration table
- server end
- client
- user program
- described registration
- 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.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 33
- 238000012545 processing Methods 0.000 claims abstract description 20
- 238000004891 communication Methods 0.000 claims description 14
- 230000004044 response Effects 0.000 claims description 13
- 230000005540 biological transmission Effects 0.000 claims description 10
- 238000012423 maintenance Methods 0.000 claims description 5
- 238000001514 detection method Methods 0.000 claims description 4
- 230000006870 function Effects 0.000 description 14
- 238000005314 correlation function Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 238000012217 deletion Methods 0.000 description 4
- 230000037430 deletion Effects 0.000 description 4
- 238000000151 deposition Methods 0.000 description 3
- 235000012093 Myrtus ugni Nutrition 0.000 description 2
- 244000061461 Tema Species 0.000 description 2
- 230000009471 action Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- HAAITRDZHUANGT-UHFFFAOYSA-N 1-[2-[(7-chloro-1-benzothiophen-3-yl)methoxy]-2-(2,4-dichlorophenyl)ethyl]imidazole;nitric acid Chemical compound O[N+]([O-])=O.ClC1=CC(Cl)=CC=C1C(OCC=1C2=CC=CC(Cl)=C2SC=1)CN1C=NC=C1 HAAITRDZHUANGT-UHFFFAOYSA-N 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 210000001072 colon Anatomy 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
Images
Abstract
The invention discloses a registry system and an operation method thereof, relating to the field of computer systems, and overcoming the problem that the workload of modifying related codes of a called registry in software is larger when a user program is transplanted in the prior art. The method comprises the steps: a registry server end opens a registry storage file according to read configuration files, the registry server end receives operation instructions transmitted by a user program via a registry client end; when the user program has the operation authority, the registry server end executes the received operation instructions in the registry storage file through a registry operation processing layer; the registry server end transmits the executed results of the operation instructions to the registry client end, and the registry client end returns the executed results to the user program by a registry dynamic link library. The embodiment of the invention is mainly applicable to computer operation systems.
Description
Technical field
The present invention relates to field of computer, relate in particular to a kind of registry system and operation method.
Background technology
Along with improving constantly of software development scale and level, the software spanning operation system platform is transplanted also becomes more prevalent demand, arrives under the LINUX/UNIX system such as the software transplanting that will operate on the WINDOWS operating system.And WINDOWS operating system is as outstanding desktop operating system, and the registration table function that it provides the not only very powerful software that is also operated on the WINDOWS operating system by great majority of function is used.
Yet the inventor finds in the prior art these to be operated in software transplanting on the WINDOWS operating system on other operating systems the time, owing to not having corresponding registration table on other operating systems, have in the software on operating in WINDOWS operating system when calling the function that registration table realizes, just need to revise the code that calls the registration table correlation function in this software, and the workload of revising described correlative code is larger, and amended software transplanting also is difficult to guarantee to compatibility and the stability under other operating systems.
Summary of the invention
Embodiments of the invention provide a kind of registry system and operation method, the code of having realized need not revising this software based on this registry system just can so that this software is transplanted under the different operating system platforms easily, carry out the workload of code revision when having reduced software transplanting.
For achieving the above object, embodiments of the invention adopt following technical scheme:
A kind of operation method of registry system, the registration table storage file in the described registry system is the XML form, and user program adopts the registration table dynamic link library to carry out compiling link, and described method comprises:
The registration table server end is opened described registration table storage file according to the configuration file that reads;
The registration table server end receives the operational order that described user program sends by the registration table client;
When the registration table server end has operating right at described user program, in described registration table storage file, carry out the described operational order that receives by the registry operations processing layer;
The registration table server end sends the execution result of described operational order to described registration table client, returns to described user program by described registration table client by the registration table dynamic link library.
Described registration table server end receives described user program: the registration table server end receives and calls described registration table dynamic link library by described user program, and the operational order that is sent by the registration table client of described registration table dynamic link library call.
Described registration table server end receives before the operational order of described user program by the transmission of registration table client, also comprises:
Described registration table server end receives the connection request instruction that described registration table client sends;
The response message of the described connection request instruction that described registration table server end sends and receives is given described registration table client;
Described registration table client connects with described registration table server end behind described response message.
In the operation method of described registry system, described registration table server end receives before the operational order of described user program by the transmission of registration table client, also comprises:
Described registration table server end receives the log-on message that described registration table client sends;
Whether described registration table server end detects the described log-on message that receives correct;
Described registration table server end sends login failure message to described registration table client when detecting described log-on message mistake;
Described registration table client stops the described registration table server end of access after described login failure message, and by described registration table dynamic link library described login failure message is returned to described user program.
In the operation method of described registry system, described registration table server end is detecting the described log-on message that receives when correct, sends login success message to described registration table client;
Described registration table client is after login success message, and described registration table server end is given in the transmit operation instruction;
Described registration table server end receives user program:
Described registration table server end receives the operational order that described registration table client sends after the login success message.
In the operation method of described registry system, also comprise:
Described registration table server end detects the user program that logins successfully and whether has operating right;
Described registration table server end is when detecting described user program and do not have operating right, and the transmit operation error message is given described registration table client, and returns to user program by the registration table client by the registration table dynamic link library.
The operation method of described registry system also comprises:
Described registration table server end receives the de-registration request that described registration table client sends;
Described registration table server end is nullified the log-on message of described registration table client.
A kind of registry system, user program adopt the registration table dynamic link library to carry out compiling link, and this system comprises: the registration table storage file of XML form;
The registration table server end, be used for opening the registration table storage file according to the configuration file that reads, receive the operational order that described user program sends by the registration table client, when described user program has operating right, in described registration table storage file, carry out received operational order by the registry operations processing layer, send the execution result of described operational order to described registration table client;
The registration table client, be used for receiving the operational order that described user program sends, send described operational order to the registration table server end, receive the execution result of the described operational order of described registration table server end transmission, and return to user program by the registration table dynamic link library;
The registry operations processing layer is for the treatment of maintenance, operation and the control of authority of data in the registration table storage file;
The registration table dynamic link library is used for calling the registration table client or offering when user program is transplanted calling;
Registration table communication protocol is for the rule of communication of standard registration table server end and registration table client.
In the described registry system, described registration table server end also is used for receiving the connection request instruction that described registration table client sends, and the response message that sends the described connection request instruction that receives is to described registration table client.
In the described registry system, described registration table server end also is used for receiving the log-on message that described registration table client sends, whether and it is correct to detect described log-on message, when detecting described log-on message mistake, sends login failure message to described registration table client;
Perhaps described registration table server end also is used for sending login success message to described registration table client detecting described log-on message when correct; Perhaps
Described registration table server end also is used for receiving the de-registration request that described registration table client sends, and nullifies the log-on message of described registration table client.
In the described registry system, whether described registration table server end also has operating right for detection of the user program that logins successfully, and when detecting described user program and do not have operating right, the transmit operation error message is given described registration table client.
In the described registry system, described registration table client also is used for sending the connection request instruction, and receives the described connection request instruction response message that the registration table server end sends, and connects with described registration table server end.
In the described registry system, described registration table client also is used for sending log-on message to the registration table server end, and receive login failure message from described registration table server end, and return to described user program by the described login failure message that the registration table dynamic link library will receive; Perhaps
Described registration table client also is used for receiving login success message from described registration table server end; Perhaps
Described registration table client also is used for sending de-registration request to described registration table server end.
In the described registry system, described registration table client also is used for receiving the operating mistake message that the registration table server sends, and returns to user program by the described operating mistake message that the registration table dynamic link library will receive.
The registry system that the embodiment of the invention provides, by making up the registration table storage file of XML form in the operating system of any type, and the user program that needs is called the registration table function links the registration table dynamic link library when the development phase compiles.When described user program calls described registration table storage file, open described registration table storage file by the registration table server end according to the configuration file that reads, then, and when described user program has operating right, in described registration table storage file, carry out the described operational order that receives by the registry operations processing layer.After described operational order executes, send the execution result of described operational order to described registration table client, return to user program by the registration table client by the registration table dynamic link library.
Described user program is by calling the registration table client and described registration table server end carries out data communication, described registration table server end is according to the operational order of user program simultaneously, carry out the associative operation of registration table storage file by the registry operations processing layer, thereby realized needing to call in the described user program function of registration table.Compared with prior art, the embodiment of the invention need not be revised the code of user program, just described user program can be transplanted under the operating system platform of any type, have been solved the larger problem of workload of when user program is transplanted, revising the code that calls the registration table correlation function in this software in the prior art.The registry system that in addition can also the embodiment of the invention provides can also realize in the WINDOWS system the substituting realization of lightweight of registration table function.
Description of drawings
In order to be illustrated more clearly in the embodiment of the invention or technical scheme of the prior art, the below will do to introduce simply to the accompanying drawing of required use in embodiment or the description of the Prior Art, apparently, accompanying drawing in the following describes only is some embodiments of the present invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain according to these accompanying drawings other accompanying drawing.
Fig. 1 is the operation method process flow diagram of embodiment 1 registry system;
Fig. 2 is the structural drawing of embodiment 1 registry system;
Fig. 3 is the operation method process flow diagram of embodiment 2 registry system;
Fig. 4 is the structural drawing of embodiment 2 registry system.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the invention, the technical scheme in the embodiment of the invention is clearly and completely described, obviously, described embodiment only is the present invention's part embodiment, rather than whole embodiment.Based on the embodiment among the present invention, those of ordinary skills belong to the scope of protection of the invention not making the every other embodiment that obtains under the creative work prerequisite.
Embodiment 1:
The embodiment of the invention provides a kind of operation method of registry system, and the registration table storage file in the described registry system is the XML form, and user program adopts the registration table dynamic link library to carry out compiling link, and as shown in Figure 1, the method comprises the steps:
101, the registration table server end is opened described registration table storage file according to the configuration file that reads.
Because the file layout of described registration table storage file is (Extens ible Markup Language, extend markup language), thereby the registration table storage file of this XML form can be structured under any operating system.
This registration table storage file is used for the information of storage registration table, and this registration table storage file can only by the access of registration table service server end, not allow other processes to conduct interviews when operation.The registration table storage file can leave diverse location in according to different operating system, such as follows by code definition:
LINUX/UNUX：
/etc/reg.dat
WINDOWS：
％WINDOWS％\sys?tem32\etc\reg.dat
Generalized case, this registration table storage file is set to hidden file, the registration table storage file position of above definition is default location, can also change the registration table storage file by arranging in the configuration file, and this configuration file can leave in such as upper/lower positions according to different operating system:
LINUX/UNUX：
/etc/reg.conf
WINDOWS：
％WINDOWS％\sys?tem32\etc\reg.conf
Described registration table storage file can also define data layout and the semanteme thereof of storing in the described registration table storage file by the registry information form, and can process by the java standard library GDOME2 that increases income (Gnome DOM Engine Version 2) the registration table storage file of described XML form.
Wherein, the data layout in the described registry information form can carry out as giving a definition:
<SYS_REG_ROOT>
<HKEY_CLASSES_ROOT>
</HKEY_CLASSES_ROOT>
<HKEY_CURRENT_USER>
<Environment>
</Environment>
<Software>
<ANY?COMPANY?NAME1>
</ANY?COMPANY?NAME1>
<ANY?COMPANY?NAME2>
</ANY?COMPANY?NAME2>
<！--
…
-->
<ANY?COMPANYNAMEn>
</ANY?COMPANY?NAMEn>
</Software>
</HKEY_CURRENT_USER>
<HKEY_LOCAL_MACHINE>
<HARDWARE>
</HARDWARE>
<SECURITY>
</SECU?RITY>
<SOFTWARE>
<ANYCOMPANY?NAME1>
</ANY?COMPANY?NAME?1>
<ANY?COMPANY?NAME2>
</ANY?COMPANY?NAME2>
<！--
-->
<ANY?COMPANY?NAMEn>
</ANY?COMPANY?NAMEn>
<FoUnder?allow＝″root，usera″p?riviledge＝″root：1，2，4|usera：2，4″>
<EgovDepartment>
<SoftwareA?allow＝″usera，userb″
priviledge＝″usera：2，4|userb：4″>
<SeffingltemA?t＝″1″allow＝″usera″
priviledge＝″usera：2，4″>settingNumberValue</SettingltemA>
<SettingltemB?t＝″2″>settingHexValue</SettingltemB>
<SettingltemC
t＝″3″>settingSt?ringValue</SettingltemC>
</SoftwareA>
<SoftwareB>
</SoftwareB>
<！--
-->
<Software_n>
</Sofrware_n>
</EgovDepartment>
<OtherNode>
</OtherNode>
</Founder>
</SOFTWARE>
<SYSTEM>
</SYSTEM>
</HKEY_LOCAL_MACHINE>
<HKEY_USERS>
</HKEY_USERS>
<HKEY_CURRENT_CONFIG>
</HKEY_CURRENT_CONFIG>
</SYS_REG_ROOT>
Wherein, the semantic information that described data layout is corresponding is:
The category-A node:
＜SYS_REG_ROOT/〉node is corresponding to the root node in the WINDOWS registration table;
＜HKEY_CLASSES_ROOT/〉node is corresponding to the HKEY_CLASSES_ROOT node in the WINDOWS registration table;
＜HKEY_CURRENT_USER/〉node is corresponding to the HKEY_CURRENT_USER node in the WINDOWS registration table;
＜HKEY_LOCAL_MACHINE/〉node is corresponding to HKEY_LOCAL_MACHINE node in the WINDOWS registration table;
＜HKEY_USERS/〉node is corresponding to the HKEY_USERS node in the WINDOWS registration table;
＜HKEY_CURRENT_CONFIG/〉the HKEY_CURRENT_CONFIG node of the corresponding WINDOWS registration table of node.
The category-B node:
＜HKEY_CURRENT_USER/〉under＜Environment/〉node, generally be used for the relevant setting of storage system environmental variance;
＜HKEY_CURRENT_USER/〉under＜Software/〉node, generally be used for depositing the configuration information of each software, its lower generally having than multinode, these nodes greatly mainly with company's English name as nodename, this node and＜HKEY_LOCAL_MACHINE/〉under＜SOFTWARE/ node in most cases is synchronous;
＜HKEY_LOCAL_MACHINE/〉under＜HARDWARE/〉be commonly used to deposit the hardware relevant information;
＜HKEY_LOCAL_MACHINE/〉under＜SECURITY/〉node, be commonly used to deposit safety relevant information is set;
＜HKEY_LOCAL_MACHINE/〉under＜SOFTWARE/〉node, this node and＜HKEY_CURRENT_USER/〉under＜Software/〉the node most applications is synchronous, below explanation is all take＜HKEY_LOCAL_MACHINE/〉under＜SOFTWARE/〉node is as example.
The C category node:
Generally speaking＜HKEY_LOCAL_MACHINE/〉under＜SOFTWARE/〉have under the node much with the nodes of company's English name name, these nodes can be referred to as enterprise's node.Generally can have some nodes with department's English name name under the described enterprise node, can be referred to as department's node, described department node is not necessarily.Generally have the node of several dbase names under the described department node, can be called for short the software node, be used for depositing the concrete registry information of each software and configuration information, because department's node not necessarily, so the software node is directly built under enterprise's node sometimes.Have some configuration item nodes under the described software node and can referred to as configuration node, be used for depositing each configuration information.
The concrete different control of authority of all kinds of different nodes, do not allow with control of authority information such as category-A node and category-B node, also can not come into force even perhaps be provided with authority information, and the C category node can be as required with control of authority information, its form can be defined as:
A1low==" " deny=" " priviledge=" " privi 1edgetype=" ", as:
<Founder?allow＝″root，usera″priviledge＝″root：1，2，4|usera：2，4″/>
Wherein deposit the user who is set up authority among the a11ow, a plurality of users separate with the half-angle comma; Priviledge represents set authority, and each user's authority separates with vertical line, separates with colon between user and the authority section, and each authority credentials separates with comma in the authority section; The user who is provided with concrete power limit among allow and the priviledge has the authority of corresponding authority credentials.
In addition, even the not explicit authority that arranges under the default situations, all users have read right to arbitrary node, unless clearly be provided with attribute " priviledgetype=" explicitly " " on the node, just only have so the explicit user who is provided with Authorization Attributes that corresponding authority is arranged.Set authority has inheritance, and the authority that namely defines in father node or grandfather's node can be inherited the node to the descendants automatically.
Configuration node can be defined as follows:
<Set?t?ingI?temA?t＝″1″allow＝″usera″privil?edge＝″usera：2，4″>set?t?ingNumberVa?lue</Set?t?ingI?temA>
<SettingItemB?t＝″2″>settingHexValue</SettingItemB>
<SettingI?temC?t＝″3″>set?t?ingStringVa?lue</SettingI?temC>
Above three all is configuration node, and wherein the implication of t is:
Value is that the attribute type that 1 this configuration node of expression is deposited is numeric type; Value is that the attribute type that 2 these configuration nodes of expression are deposited is binary type; Value is that the attribute type that 3 these configuration nodes of expression are deposited is character string type.
Without child node, internodal content is the value of configuration item under the configuration node.A configuration node is a configuration item, the situation of the corresponding two or more configuration items of a configuration node can not occur, the situation of the corresponding configuration node of two or more configuration items also can not occur.
102, the registration table server end receives the operational order that described user program sends by the registration table client.
The operational order that described registration table client user program sends, and described operational order sent to described registration table server end.Then described registration table server end is from the described operational order of this registration table client.
103, the registration table server end is carried out the described operational order that receives by the registry operations processing layer in described registration table storage file when described user program has operating right.Because the operating right that each user program has is different, can carry out the read operation of registration table such as some user program, but can not carry out write operation.At this moment just need to carry out judge first the operating right of described user program before telling operational order, and then guarantee to carry out according to correct authority the associative operation of described registration table storage file.
104, the registration table server end send described operational order execution result to described registration table client, return to described user program by described registration table client by the registration table dynamic link library.When described user program has corresponding operating right, as carrying out the deletion action of registration table storage file, after this operational order is complete, the registration table server end can send to the execution result of described operational order described registration table client, and return to user program by the registration table client by the registration table dynamic link library, so that user program can be known the operation result of knowing described operational order.Communicating by letter of above-mentioned registration table client and described registration table server end can concurrently be carried out.
Said method is in implementation process, by making up the registration table storage file of XML form in the operating system of any type, and by the described registration table storage file of described registration table server end exclusive access.Then described registration table server end is by receiving user program by the operational order of registration table client transmission, when described user program has corresponding operating right, carry out described operational order and its execution result and send to described registration table client, return to user program by the registration table client by the registration table dynamic link library.Thereby can just described user program can be transplanted under the operating system platform of any type so that the user need not revise the code of user program, and realize needing to call in the described user program function of registration table.Compared with prior art, reduced and revised the workload of calling registration table correlation function code in this software when user program transplanted.
The embodiment of the invention also provides a kind of registry system, wherein user program adopts the registration table dynamic link library to carry out compiling link, as shown in Figure 2, this system comprises: the registration table storage file 21 of XML form, registration table server end 22, registration table client 23, registry operations processing layer 24, registration table dynamic link library 25 and registration table communication protocol 26.
Wherein, the registration table storage file 21 of XML form, the information that is used for storing registration table.Registration table server end 22, be used for opening the registration table storage file according to the configuration file that reads, receive the operational order that described user program sends by the registration table client, when described user program has operating right, in described registration table storage file, carry out received operational order by the registry operations processing layer, send the execution result of described operational order to described registration table client.
Registry operations processing layer 24 is for the treatment of maintenance, operation and the control of authority of data in the registration table storage file.Registration table dynamic link library 25 is used for calling the registration table client or offering when user program is transplanted calling.Registration table communication protocol 26 is for the rule of communication of standard registration table server end and registration table client.
Adopt user program described in this system by calling the registration table client and described registration table server end carries out data communication, described registration table server end is according to the operational order of user program simultaneously, carry out the associative operation of registration table storage file by the registry operations processing layer, thereby realized needing to call in the described user program function of registration table.Compared with prior art, the embodiment of the invention need not be revised the code of user program, just described user program can be transplanted under the operating system platform of any type, have been solved the larger problem of workload of when user program is transplanted, revising the code that calls the registration table correlation function in this software in the prior art.
Embodiment 2:
The embodiment of the invention provides a kind of operation method of registry system, and the registration table storage file in the described registry system is the XML form, and user program adopts the registration table dynamic link library to carry out compiling link, and as shown in Figure 3, the method comprises the steps:
301, the registration table server end is opened described registration table storage file according to the configuration file that reads.The description of the registration table storage file among described registration table storage file and the embodiment 1 is identical.
302, when user program calls the registration table storage file, by calling described registration table dynamic link library, and by described registration table dynamic link library call registration table client, before by described registration table client transmit operation instruction, described registration table server end can connect according to registration table communication protocol and described registration table client.Can realize as follows:
302A, described registration table server end receive the connection request instruction that described registration table client sends;
302B, described registration table server end send the response message of the described connection request instruction that receives to described registration table client;
302C, described registration table client connect with described registration table server end behind described response message.
Such as, the registration table server end is monitored the connection request whether 8228 ports have the registration table client to send.When client connects 8228 port of upper registration table server end, send the data of 4 hexadecimal values, such as 0xff 0x00 0xff 0x00.Then the registration table server end receives the connection request data of described registration table client, check when finding to be 0xff 0x00 0xff 0x00, then newly set up a thread, monitor any one idle port such as port B, and the port numbers of idle port is returned to the registration table client.
The response message of registration table client connection request, check when finding to be 0xff 0x00 0xff 0x000x** 0x**, convert 0x** 0x** to port numbers B, this moment, the registration table client was closed connection, reconnect the port B of registrar, after the connection, send 4 sexadecimal Value Data 0xff 0x00 0xff0x01.The port B of registrar sends 4 hexadecimal values to the registration table client: 0xff 0x00 0xff0x01.When client arrives return messages, check when finding to be 0xff 0x00 0xff 0x01, this moment, connection was successfully established.
303, after described registration table server end and described registration table client connect, described registration table server end receives the log-on message that described registration table client sends, and whether detect the described log-on message that receives correct.
If described registration table server end is when detecting described log-on message mistake, send login failure message to described registration table client.Described registration table client then can stop accessing described registration table server end, and by described registration table dynamic link library described login failure message be returned to described user program after described login failure message;
If described registration table server end is detecting the described log-on message that receives when correct, send login success message to described registration table client.Then described registration table client is after login success message, and described registration table server end is given in the transmit operation instruction.
304, the registration table server end receives described operational order.Described operational order calls described registration table dynamic link library by described user program, and sends to described registration table server end by described registration table dynamic link library call registration table client.
305, whether the described user program that logins successfully of described registration table server end detection has operating right.Because the operating right that each user program has is different, can carry out the read operation of registration table such as some user program, but can not carry out write operation.At this moment just need to carry out judge first the operating right of described user program before telling operational order, and then guarantee to carry out according to correct authority the associative operation of described registration table storage file.
If described registration table server end is when detecting described user program and do not have operating right, the transmit operation error message is given described registration table client, and returns to user program by the registration table client by the registration table dynamic link library.
306, when the registration table server end is detecting described user program and has operating right, in described registration table storage file, carry out the described operational order that receives by the registry operations processing layer.Described registry operations processing layer is for the treatment of maintenance, operation and the control of authority of data in the registration table storage file.
For example, the described operational order that will carry out can for:
READ＜NodePath〉and then parameter＜NodePath 〉, the value of certain node,＜NodePath are obtained in expression〉and the XPATH path of the node of indicating to obtain;
WRITE＜NodePath〉＜Va 1ue〉and then two parameter＜NodePath〉＜value 〉, expression arranges the value of certain node,＜NodePath〉the XPATH path of the node of indicating to arrange,＜Value〉the expression value that will arrange, if node/path that XPATH represents does not exist, then can automatically set up corresponding node/path;
CREATE＜NodePath〉and then parameter＜NodePath 〉, certain node,＜Nodepath are set up in expression〉and the XPATH path of the node of indicating to set up;
DELETE＜NodePath〉and then parameter＜NodePath 〉, certain node of expression deletion,＜NodePath〉and the XPATH path of the node of indicating to delete;
307, the registration table server end send described operational order execution result to described registration table client, return to user program by the registration table client by the registration table dynamic link library.Such as, can carry out the deletion action of registration table storage file, after this operational order is complete, the registration table server end can send to the execution result of described operational order described registration table client, and return to user program by the registration table client by the registration table dynamic link library, so that user program can be known the operation result of knowing described operational order.
Described registration table dynamic link library is to offer the dynamic link library of arbitrary software developer in order to transplant and/or to call, this dynamic link library is in intrinsic call registration table client, the function interface consistent with the WINDOWS registry functions outwards is provided, therefore only need to when compiling, specify this registration table dynamic link library is compiled together, can realize the registration table function of LINUX/UNIX, or realize the substituting realization of lightweight of registration table function in the WINDOWS system.
Interface function is as follows:
/ * open certain registry entry */
int?RegOpenKeyEx(const?char*plabel，cons?t?char*pkey，/*not?use*/uns?igned?1ong?reserved，/*not?use*/uns?igned?1ong?mode，HKEY*phKey)；
/ * obtain the value * of registration table node/
int?RegQueryVa?1ueEx(HKEY?hKey，cons?t?char*pkey，/*not?use*/uns?igned?1ong*preserved，/*not?use*/uns?igned?long*ptype，uns?igned?char*pch，uns?igned?long*ps?ize)；
/ * arrange the value * of registration table node/
intRegSetVa?lueEx(HKEY?hKey，cons?t?char*pkey，/*not?use*/uns?igned?long?reserved，/*not?use*/uns?igned?1ong?type，cons?t?char*pya?lue，uns?igned?1ong?size)；
/ * set up registry node */
int?RegCrea?teKey(HKEY?hKey，cons?t?char*pkey，HKEY*phRet)；
/ * deletion registry node */
int?RegDeleteKey(HKEY?hKey，const?char*pkey)；
/ * close the registry entry * that opens/
int?RegCloseKey(HKEY?hKey)；
308, after the operational order that described user program calls the registration table storage file is finished, the de-registration request that sends by described registration table client is to described registration table server end.Receive the de-registration request of described registration table client transmission when described registration table server end, described registration table server end is nullified the log-on message of described registration table client.Then described registration table client disconnects and being connected of described registration table server end.Above-mentioned user program is logined described registration table server end and can concurrently be carried out by calling the registration table client, can allow a plurality of user programs to login described registration table server end by calling separately corresponding registration table client, and then access described registration table storage file by described registration table server end.
Need not revise in the code situation of user program by the embodiment of the invention that above-mentioned steps is described, just described user program can be transplanted under the operating system platform of any type, have been solved the larger problem of workload of when user program is transplanted, revising the code that calls the registration table correlation function in this software in the prior art.
The embodiment of the invention also provides a kind of registry system, and as shown in Figure 4, this system comprises: the registration table storage file 41 of XML form, registration table server end 42, registration table client 43, registry operations processing layer 44, registration table dynamic link library 45 and registration table communication protocol 46.
Wherein, the registration table storage file 41 of XML form is used for the information of storage registration table, and is realized the definition of the structure, a node, back end, nodal community, property value etc. of described registration table storage file by the registry information form.Support the registration table storage file of storehouse operation XML form by GDOME2.
Registration table server end 42, be used for opening the registration table storage file according to the configuration file that reads, receive the operational order that user program sends by the registration table client, when described user program has operating right, in described registration table storage file, carry out received operational order by the registry operations processing layer, send the execution result of described operational order to described registration table client.
Described registration table server end 42 also is used for receiving the connection request instruction that described registration table client sends, and the response message that sends the described connection request instruction that receives is to described registration table client.Described registration table server end 42 also is used for receiving the log-on message that described registration table client sends, whether and it is correct to detect described log-on message, when detecting described log-on message mistake, send login failure message to described registration table client, perhaps detect described log-on message when correct, sending login success message to described registration table client.
Whether described registration table server end 42 also has operating right for detection of the described user program that logins successfully, and when detecting described user program and do not have operating right, the transmit operation error message is given described registration table client.Described registration table server end 42 also is used for receiving the de-registration request that described registration table client sends, and nullifies the log-on message of described registration table client.
Described registration table client 43 also is used for sending the connection request instruction, and receives the described connection request instruction response message that the registration table server end sends, and connects with described registration table server end.
Described registration table client 43 also is used for sending log-on message to the registration table server end, and from described registration table server end reception login failure message, and by the registration table dynamic link library the described login failure message that receives is returned to described user program, or receive login success message from described registration table server end.
Described registration table client 43 also is used for receiving the operating mistake message that the registration table server sends, and by the registration table dynamic link library the described operating mistake message that receives is returned to user program.
Described registration table client 43 also is used for sending de-registration request to described registration table server end.
Registry operations processing layer 44 is for the treatment of maintenance, operation and the control of authority of data in the registration table storage file.Registration table dynamic link library 45 is used for calling the registration table client or offering when user program is transplanted calling.Registration table communication protocol 46 is for the rule of communication of standard registration table server end and registration table client.
Adopt user program described in this system by calling the registration table client and described registration table server end carries out data communication, described registration table server end is according to the operational order of user program simultaneously, carry out the associative operation of registration table storage file by the registry operations processing layer, thereby realized needing to call in the described user program function of registration table.Compared with prior art, the embodiment of the invention need not be revised the code of user program, just described user program can be transplanted under the operating system platform of any type, have been solved the larger problem of workload of when user program is transplanted, revising the code that calls the registration table correlation function in this software in the prior art.
The embodiment of the invention is mainly used in the computer operating system, the code of having realized need not revising this software based on this registry system just can so that this software is transplanted under the different operating system platforms easily, carry out the workload of code revision when having reduced software transplanting.
Through the above description of the embodiments, the those skilled in the art can be well understood to the present invention and can realize by the mode that software adds essential common hardware, can certainly pass through hardware, but the former is better embodiment in a lot of situation.Based on such understanding, the part that technical scheme of the present invention contributes to prior art in essence in other words can embody with the form of software product, this computer software product is stored in the storage medium that can read, floppy disk such as computing machine, hard disk or CD etc., comprise some instructions with so that computer equipment (can be personal computer, server, the perhaps network equipment etc.) carry out the described method of each embodiment of the present invention.
The above; be the specific embodiment of the present invention only, but protection scope of the present invention is not limited to this, anyly is familiar with those skilled in the art in the technical scope that the present invention discloses; can expect easily changing or replacing, all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection domain of described claim.
Claims (14)
1. the operation method of a registry system is characterized in that, the registration table storage file in the described registry system is the XML form, and user program adopts the registration table dynamic link library to carry out compiling link, and described method comprises:
The registration table server end is opened described registration table storage file according to the configuration file that reads;
The registration table server end receives the operational order that described user program sends by the registration table client;
When the registration table server end has operating right at described user program, in described registration table storage file, carry out the described operational order that receives by the registry operations processing layer;
The registration table server end sends the execution result of described operational order to described registration table client, returns to described user program by described registration table client by the registration table dynamic link library.
2. the operation method of registry system according to claim 1, it is characterized in that, described registration table server end receives described user program: the registration table server end receives and calls described registration table dynamic link library by described user program, and the operational order that is sent by the registration table client of described registration table dynamic link library call.
3. the operation method of registry system according to claim 1 and 2 is characterized in that, described registration table server end receives before the operational order of described user program by the transmission of registration table client, also comprises:
Described registration table server end receives the connection request instruction that described registration table client sends;
The response message of the described connection request instruction that described registration table server end sends and receives is given described registration table client;
Described registration table client connects with described registration table server end behind described response message.
4. the operation method of registry system according to claim 1 and 2 is characterized in that, described registration table server end receives before the operational order of described user program by the transmission of registration table client, also comprises:
Described registration table server end receives the log-on message that described registration table client sends;
Whether described registration table server end detects the described log-on message that receives correct;
Described registration table server end sends login failure message to described registration table client when detecting described log-on message mistake;
Described registration table client stops the described registration table server end of access after described login failure message, and by described registration table dynamic link library described login failure message is returned to described user program.
5. the operation method of registry system according to claim 4 is characterized in that, described registration table server end is detecting the described log-on message that receives when correct, sends login success message to described registration table client;
Described registration table client is after login success message, and described registration table server end is given in the transmit operation instruction;
Described registration table server end receives user program:
Described registration table server end receives the operational order that described registration table client sends after the login success message.
6. the operation method of registry system according to claim 4 is characterized in that, also comprises:
Described registration table server end detects the user program that logins successfully and whether has operating right;
Described registration table server end is when detecting described user program and do not have operating right, and the transmit operation error message is given described registration table client, and returns to user program by the registration table client by the registration table dynamic link library.
7. the operation method of registry system according to claim 4 is characterized in that, also comprises:
Described registration table server end receives the de-registration request that described registration table client sends;
Described registration table server end is nullified the log-on message of described registration table client.
8. a registry system is characterized in that, user program adopts the registration table dynamic link library to carry out compiling link, and this system comprises: the registration table storage file of XML form;
The registration table server end, be used for opening the registration table storage file according to the configuration file that reads, receive the operational order that described user program sends by the registration table client, when described user program has operating right, in described registration table storage file, carry out received operational order by the registry operations processing layer, send the execution result of described operational order to described registration table client;
The registration table client, be used for receiving the operational order that described user program sends, send described operational order to the registration table server end, receive the execution result of the described operational order of described registration table server end transmission, and return to user program by the registration table dynamic link library;
The registry operations processing layer is for the treatment of maintenance, operation and the control of authority of data in the registration table storage file;
The registration table dynamic link library is used for calling the registration table client or offering when user program is transplanted calling;
Registration table communication protocol is for the rule of communication of standard registration table server end and registration table client.
9. registry system according to claim 8, it is characterized in that, described registration table server end also is used for receiving the connection request instruction that described registration table client sends, and the response message that sends the described connection request instruction that receives is to described registration table client.
10. registry system according to claim 8, it is characterized in that, described registration table server end also is used for receiving the log-on message that described registration table client sends, whether and it is correct to detect described log-on message, when detecting described log-on message mistake, send login failure message to described registration table client;
Perhaps described registration table server end also is used for sending login success message to described registration table client detecting described log-on message when correct; Perhaps
Described registration table server end also is used for receiving the de-registration request that described registration table client sends, and nullifies the log-on message of described registration table client.
11. registry system according to claim 8, it is characterized in that, whether described registration table server end also has operating right for detection of the user program that logins successfully, and when detecting described user program and do not have operating right, the transmit operation error message is given described registration table client.
12. registry system according to claim 8, it is characterized in that, described registration table client also is used for sending the connection request instruction, and receives the described connection request instruction response message that the registration table server end sends, and connects with described registration table server end.
13. registry system according to claim 8, it is characterized in that, described registration table client also is used for sending log-on message to the registration table server end, and receive login failure message from described registration table server end, and return to described user program by the described login failure message that the registration table dynamic link library will receive; Perhaps
Described registration table client also is used for receiving login success message from described registration table server end; Perhaps
Described registration table client also is used for sending de-registration request to described registration table server end.
14. registry system according to claim 8, it is characterized in that, described registration table client also is used for receiving the operating mistake message that the registration table server sends, and returns to user program by the described operating mistake message that the registration table dynamic link library will receive.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910244153.XA CN102117286B (en) | 2009-12-30 | 2009-12-30 | Registry system and operation method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910244153.XA CN102117286B (en) | 2009-12-30 | 2009-12-30 | Registry system and operation method thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102117286A CN102117286A (en) | 2011-07-06 |
| CN102117286B true CN102117286B (en) | 2013-02-06 |
Family
ID=44216060
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910244153.XA Expired - Fee Related CN102117286B (en) | 2009-12-30 | 2009-12-30 | Registry system and operation method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102117286B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102981811A (en) * | 2011-09-05 | 2013-03-20 | 北大方正集团有限公司 | Processing method and device of user option data |
| CN104539585B (en) * | 2014-12-05 | 2017-12-05 | 北京奇虎科技有限公司 | Method, browser client and the device of the anti-injection of browser |
| CN105912952B (en) * | 2016-05-04 | 2019-07-23 | 广州广电运通金融电子股份有限公司 | A kind of registration list service system, method and financial self-service equipment based on Linux |
| CN107122164B (en) * | 2017-03-31 | 2023-04-07 | 腾讯科技（深圳）有限公司 | Method, device, equipment and storage medium for acquiring function address and applying function address |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101221499A (en) * | 2006-11-29 | 2008-07-16 | Sap股份公司 | Method and apparatus for configuring application software |
| WO2008152515A2 (en) * | 2007-06-08 | 2008-12-18 | Accenture Global Services Gmbh | Migration of legacy applications |
| CN101403966A (en) * | 2008-11-18 | 2009-04-08 | 苏州工业园区联科信息技术有限公司 | Method for implementing portable software |
| CN101533345A (en) * | 2008-03-13 | 2009-09-16 | 中兴通讯股份有限公司 | Device for configuring information based on extensible markup language (XML) and method thereof. |
-
2009
- 2009-12-30 CN CN200910244153.XA patent/CN102117286B/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101221499A (en) * | 2006-11-29 | 2008-07-16 | Sap股份公司 | Method and apparatus for configuring application software |
| WO2008152515A2 (en) * | 2007-06-08 | 2008-12-18 | Accenture Global Services Gmbh | Migration of legacy applications |
| CN101533345A (en) * | 2008-03-13 | 2009-09-16 | 中兴通讯股份有限公司 | Device for configuring information based on extensible markup language (XML) and method thereof. |
| CN101403966A (en) * | 2008-11-18 | 2009-04-08 | 苏州工业园区联科信息技术有限公司 | Method for implementing portable software |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102117286A (en) | 2011-07-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP1872215B1 (en) | Implementing data-compatibility-based version scheme | |
| US8869043B2 (en) | System for presenting applications on instant messaging clients | |
| US7917855B1 (en) | Method and apparatus for configuring a user interface | |
| US6108712A (en) | Client-server system with central application management and providing export agent capability for retrofitting existing hardware and applications into the system | |
| US6151620A (en) | Conference messaging system | |
| US7376670B2 (en) | System and method for provisioning presence application services | |
| US7596611B1 (en) | Method and apparatus for maintaining information for use in the configuration of a client | |
| KR20100080825A (en) | Network operating system | |
| CN101529382A (en) | Common component framework | |
| CN102117286B (en) | Registry system and operation method thereof | |
| CN106487600A (en) | A kind of automatic Deployment Solution for Services of WebLogic cluster | |
| CN103049268A (en) | Naplet based application development and management system | |
| CN102262541A (en) | Method for starting dynamic configuration plug-in | |
| US20070233717A1 (en) | Generic product configuration framework for building product specific installers | |
| US7783720B1 (en) | CORBA metadata gateway to telecommunications management network | |
| Otte et al. | Towards an adaptive deployment and configuration framework for component-based distributed systems | |
| CN116107590A (en) | Implementation method and system for compatible micro-service and monomer architecture in software product development and deployment | |
| CN107015787B (en) | Method and device for designing interactive application framework | |
| US8190558B2 (en) | Non-programmatic access to enterprise messaging administration | |
| CN112925655B (en) | Decoupling system for dividing service and method thereof | |
| Morand et al. | Towards autonomic enterprise service bus | |
| KR101888792B1 (en) | Method for data communication and system comprising the same | |
| DONTU | SOFTWARE DEVELOPMENT | |
| Lhotka | Expert One-on-one Visual Basic. NET Business Objects | |
| Wessler et al. | Configuring Java Message Service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220919 Address after: 3007, Hengqin international financial center building, No. 58, Huajin street, Hengqin new area, Zhuhai, Guangdong 519031 Patentee after: New founder holdings development Co.,Ltd. Patentee after: BEIJING FOUNDER ELECTRONICS CHIEF INFORMATION TECHNOLOGY Co.,Ltd. Patentee after: BEIJING FOUNDER ELECTRONICS Co.,Ltd. Address before: 100871, Beijing, Haidian District Cheng Fu Road 298, founder building, 5 floor Patentee before: PEKING UNIVERSITY FOUNDER GROUP Co.,Ltd. Patentee before: BEIJING FOUNDER ELECTRONICS CHIEF INFORMATION TECHNOLOGY Co.,Ltd. Patentee before: BEIJING FOUNDER ELECTRONICS Co.,Ltd. |
|
| TR01 | Transfer of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20130206 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |