CN103218378A - Method for carrying out database operation based on complicated logic on basis of LDAP (lightweight directory access protocol) - Google Patents
Method for carrying out database operation based on complicated logic on basis of LDAP (lightweight directory access protocol) Download PDFInfo
- Publication number
- CN103218378A CN103218378A CN2012100251551A CN201210025155A CN103218378A CN 103218378 A CN103218378 A CN 103218378A CN 2012100251551 A CN2012100251551 A CN 2012100251551A CN 201210025155 A CN201210025155 A CN 201210025155A CN 103218378 A CN103218378 A CN 103218378A
- Authority
- CN
- China
- Prior art keywords
- ldap
- script
- database
- server
- xquery
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
According to the existing LDAP (lightweight directory access protocol), complicated logic can not be expressed in a single LDAP request message. The invention provides a method for carrying out database operation based on complicated logic on the basis of the LDAP, information relative to a script is placed in the single LDAP request message by an LDAP client end, the script is executed by an LDAP server so as to carry out the database operation with complicated logic, the LDAP request information is sent to the server, the information relative to the script is obtained by the server, according to the information, the script is obtained and executed to carry out the database operation, and the execution result of the script is in an LDAP response message and is returned to the client end. Preferably, the complicated logic can not be expressed with an LDAP filter. According to the method, the LDAP filter is not required to use, the database operation of complicated logic can be completed, and a totally novel database operation method is provided.
Description
Technical field
The present invention relates to ldap protocol, and relate to database manipulation.
Background technology
In network application, can only hold foolproof logical operation in the LDAP request based on LDAP (Lightweight Directory Access Protocol, Lightweight Directory Access Protocol).Do not have existing universal method and can allow the LDAP client in wall scroll LDAP request, to carry out flexibly/the complex logic computing, with the intricately operating database to server requests.For example, these demands can't realize usually below: client needs single request to search the project of certain condition of coupling, and this condition can't be explained by LDAP filtrator grammer.Again for example, client needs single request to upgrade/delete/or increase project, the complicated condition of this project coupling, and support primitive operation.
Cause the reason of this problem to be, the demand of LDAP client must be undertaken by server end, and very flexible/complicated logical calculated just can be finished, but the LDAP client only sends single LDAP request, and the logic of this complexity can not be expressed in the LDAP grammer in this request.In order to finish complex logic, LDAP client and ldap server must carry out the request and the response of several bouts, this has wasted a large amount of network bandwidths and has caused very big delay, and thereby the response of LDAP client in the middle of also must analyzing carry out request next time, and this has brought very big burden to the LDAP client.In addition, the client and server from different manufacturers can not well cooperate usually.
Summary of the invention
As seen, ldap protocol of the prior art can not be supported complex logic.If can provide a kind of based on database operation method ldap protocol, that can support complex logic, that will be very to have advantage.
Aspect according to the present invention in the LDAP client, provide a kind of in the LDAP client, being used to ask ldap server to have the method for the database manipulation of complex logic, it is characterized in that, comprised the steps:
I. the information relevant with script is placed in the single LDAP request message, described script is performed to carry out described database manipulation with complex logic by described server;
II. send this LDAP request message to described server;
III. receive execution result from the script in the LDAP response message of ldap server;
Wherein, the script reading database content of described complex logic, and/or change data-base content.
Aspect according to the present invention in ldap server, provide a kind of method that in ldap server, is used to have the database manipulation of complex logic, it is characterized in that, comprised the steps:
I. receive the single LDAP request message from the LDAP client, contain the information relevant with script in this message, described script is used for by described server performed to carry out described database manipulation with complex logic;
Ii. obtain the described information relevant with script;
Iii. according to the described information relevant, obtain and carry out described script, to carry out described database manipulation with script;
Iv. the execution result with script returns to described LDAP client in the LDAP response message.
According to above two aspects, the LDAP client can be carried out script by indication ldap server in single LDAP request message and carry out database manipulation, need not to use the LDAP filtrator, provide a kind of brand-new database operation method with respect to prior art, and do not needed ldap protocol is carried out any change.
According to one preferred embodiment, the script reading database content of described complex logic, and/or the change data-base content, and,
Described complex logic can't simply be expressed with the LDAP filtrator.
In this embodiment, the script of complex logic can carry out operations commonly used such as various read-writes commonly used to database, and need not to use the LDAP filtrator that is beyond expression in the LDAP request message of complex logic, remedied the blank that to finish complex logic in the prior art by single LDAP request message, the request and the response of a plurality of bouts have been avoided, saved the network bandwidth, reduced delay, and alleviated the analysis burden of LDAP client response.
Preferred embodiment the described information relevant with script comprises the file of script according to one, and described step I ii comprises:
-acquisition extracts the file of described script from described LDAP request message;
And/or,
Stored or be written into script on this ldap server, the described information relevant with script comprises the indication information of the script that indication has been stored or has been written on described ldap server, and described step I ii comprises:
-be written into the indicated script of indication information that stored, described, or selected loaded, the indicated script of described indication information.
This embodiment provides two kinds of schemes to make the used script of LDAP client indication ldap server, does not need ldap protocol is carried out any change.
According to one preferred embodiment, also contain the parameter of described database manipulation script in the described LDAP request message;
Described step I i also extracts described script argument from described LDAP request message;
Described step I ii also carries out described script according to described parameter.
This embodiment provides the support to the script input parameter, thereby provides support to input parameter to database manipulation, has stronger function.
According to a further preferred embodiment, described information relevant with script and described parameter are placed in the corresponding LDAP control element in this LDAP request message,
From corresponding LDAP control element, extract described information relevant and described parameter among the described step I i respectively with script.
This embodiment has utilized the LDAP control element in the LDAP request message to hold the information relevant with script, and/or parameter, does not need ldap protocol is carried out any change.
According to one preferred embodiment, when described script was the XQuery script, described step I comprised the steps:
-this LDAP request message receives and decodes;
-obtain the structural data in the LDAP request message, contain the described information relevant in this structural data with script;
Described step I i comprises the steps:
-extract the described information relevant with script, and be converted into the input parameter XML file of XQuery script, offer the XQuery query engine;
Described step I ii comprises the steps:
-this XQuery query engine obtains corresponding XQuery script and input parameter thereof;
-this XQuery query engine is carried out the XQuery script, ldap database is operated, and obtained the operating result of XML form;
Described step I v comprises:
-operating result of described XML form is converted to the data structure that LDAP responds;
-operating result of the data structure of LDAP response is encoded to the LDAP response message send it back the LDAP client.
Concrete application scheme when this embodiment provides the present invention to be applicable to the XQuery script.
According to a further preferred embodiment, ldap database is expressed with virtual XML view, make the XQuery script can operate virtual XML document, shine upon by a kind of general ldap directory inforamtion tree model and XSD model and finish;
Wherein, this mapping principle all is suitable for all ldap databases;
The database bottom layer realization can be XML database or non-XML database, when ldap database right and wrong XML database, the XQuery interpreter will be finished the operation of virtual XML document by the application programming interface of actual database, with all will be mapped to the visit in True Data storehouse among the XQuery to the visit of XPATH.
Concrete application scheme when this embodiment provides the present invention to be applicable to various types of ldap database.
According to one preferred embodiment, described step I v is placed on the execution result of described script in the LDAP control element in the LDAP response message, and this LDAP response message is sent to the LDAP client.
This embodiment has utilized the LDAP control element in the LDAP response message to hold the execution result of script, does not need ldap protocol is carried out any change.
One preferred embodiment in, this method also comprises the steps:
V. in carrying out described script, make a mistake/when unusual, with the described LDAP client of described script error/send it back unusually;
Described step v sends to the LDAP client with described script error/be placed on unusually in the LDAP control element in the LDAP response message with this LDAP response message.
Dishing out and feeding back of this embodiment support mistake/unusual has perfect functions more, and utilized LDAP control element in the LDAP response message to hold script error/unusual, do not need ldap protocol is carried out any change.
Description of drawings
By reading the detailed description of doing with reference to the following drawings that non-limiting example is done, other features, objects and advantages of the present invention will become more apparent:
Fig. 1 is the synoptic diagram that can be used in the virtual XML view of expressing ldap database;
Fig. 2 is a module map that is applicable to the ldap server of XML database of the present invention;
Fig. 3 is a module map that is applicable to the ldap server of non-XML database of the present invention.
Embodiment
Be elaborated below by specific embodiment.Need to prove that under the situation of not conflicting, embodiment and the feature among the embodiment among the application can make up mutually.
Inventive concept of the present invention is, uses script to carry out complicated logical operation at the ldap server end, and does not change defined ldap protocol among the RFC4511.This script can send to ldap server by the LDAP request message by the LDAP client, perhaps is pre-stored in the ldap server, and is specified by the LDAP request message by the LDAP client.
The language of Script Programming is also unrestricted:
-can be the specific or privately owned script of manufacturer;
-can be existing script, Javascript for example, Tcl, Perl, Python, object C (Objective C) or the like;
-being in the purpose that improves performance, script also can be write by Java, C or the C++ as plug-in unit, and these plug-in units can dynamically or statically be compiled and be written into.
In one embodiment, the LDAP client is placed on script file in the single LDAP request message, and this LDAP request message is sent to ldap server.Ldap server is accepted this LDAP request message, therefrom extracts this script, and carries out this script, carrying out database manipulation, and the result of script executing is sent it back the LDAP client in the LDAP response message.This embodiment will hereafter be described in more detail.
In another embodiment, script file has been pre-stored in the ldap server, perhaps is preloaded in the storer of ldap server.The LDAP client will be indicated the information of this script file, and for example the title of this script file is placed in the single LDAP request message, and this LDAP request message is sent to ldap server.Ldap server is according to this information, and selected corresponding script, and carry out this script carrying out database manipulation, and sends it back the LDAP client with the result of script executing in the LDAP response message.
In addition, the parameter of database manipulation also can be sent to ldap server by the LDAP request message by the LDAP client.
One preferred embodiment in, the information of above script file or indication script file, and the parameter of database manipulation can be placed in the various LDAP request messages as LDAP control element (LDAP control), for example, SearchRequest, ModifyRequest, DeleteRequest, AddRequest, ModifyDNRequest is among the ExtendedRequest.The actual LDAP control element that uses can be consulted by LDAP client and ldap server in advance, what for example represent that this control element holds for the control element of certain particular value with OID is script file, and what represent that this control element holds for the control element of another particular value with OID is parameter.Correspondingly, ldap server can be resolved received LDAP request message, and therefrom extracts the information of script file or indication script file in the control corresponding element, and the parameter of database manipulation.This embodiment will hereafter be described in more detail.
Ldap server returns to the LDAP client with the execution result of script in the LDAP response message, for example, SearchResEntry, SearchResDone, ModifyResponse, DeleteResponse, AddResponse, ModifyDNResponse, ExtendedResponse is among the IntermediateResponse.Preferably, ldap server is placed on the execution result of script in the LDAP control element in the LDAP response message, and this LDAP response message is sent to the LDAP client.The actual LDAP control element that uses can be consulted by LDAP client and ldap server in advance.
Ldap server makes a mistake in carrying out script/when unusual, and can be with script error/send it back unusually LDAP client.Preferably, script error/unusually also can be placed in the various LDAP response messages as LDAP control element (LDAP control), for example, SearchResEntry, SearchResDone, ModifyResponse, DeleteResponse, AddResponse, ModifyDNResponse, ExtendedResponse is among the IntermediateResponse.The actual LDAP control element that uses can be consulted by LDAP client and ldap server in advance.
The disclosure also provides embodiment more concrete, that use the XQuery script.In this embodiment, in order to be implemented in the performed XQuery script of ldap server end, and do not change the standard by the defined XQuery of W3C, DIT (directory information tree) can be carried out to the mapping of XML.
Other uses though the disclosure is not limited in the ldap protocol level, and it can provide the concrete and general realization that does not still have at present.It is based on the mapping of general DIT to XML grammer (XML Scheme).Each ldap server all should have DIT model and the syntactic definition of LDAP, and it can be mapped as general XML grammer.And the model of LDAP grammer and DIT is not limited yet.Manufacturer server can be expanded the XML grammer that is shone upon according to their privately owned characteristic.
Concrete mapping example can be as shown in Figure 1, wherein
-one LDAP item is mapped as one＜Entry〉element;
-one＜Entry〉element contains one＜RDN_AVP_List〉element;
One＜RDN_AVP_List of ■〉element contain at least one＜RDN_AVP element;
◆ one＜RDN_AVP〉element contains one＜RDN_NAME〉element and one＜RDN_VALUE〉element;
-one＜Entry〉element has one＜ObjectClass_List〉element;
One＜ObjectClass_List of ■〉element contain at least one＜ObjectClass element;
◆ one＜ObjectClass〉element contains one＜OCName〉element and one＜Attribute_List〉element;
● one＜Attribute_List〉element contains 0 and above＜Attribute〉element;
One＜Attribute of ■〉element contains one＜AttributeName〉element and 0 and above＜AttributeValue〉element;
-one＜Entry〉element has one＜SubEntry_List〉element;
One＜SubEntry_List of ■〉element contain 0 or a plurality of＜Entry element.
Each LDAP data type all should be mapped to corresponding XSD (XML syntactic definition) data type.
Be included in the parameter of the database manipulation in the LDAP request message, promptly script argument also need be mapped in the virtual XML file at the ldap server end and be transferred to the XQuery engine, and this XQuery engine is carried out the XQuery script.
In general, the result of the script of XQuery engine output is the XML form.Ldap server should be understood the result's of this XML form grammer, and, this result is converted to the LDAP response message sends it back the LDAP client.
In this case, the XQuery script should be known the grammer of the virtual XML file that is shone upon by parameter, LDAP DIT database and LDAP response message in the LDAP request.
Script can utilize the existing characteristic of XQuery and XPATH fully, to realize complicated logic and to search in virtual XML file.
Ldap database upgrades and can recommend the XQuery update mechanism to be supported by new W3C.The expanded function that manufacturer also can introduce in XQuery 1.0 engines is supported the renewal of transaction data base, and does not use the XQuery update mechanism.
Ldap database can be the database that the ldap directory inforamtion tree is mapped as the XML thesaurus, database that also can right and wrong XML thesaurus.Both of these case is with more detailed explanation in the embodiment below.
Fig. 2 is a module map that is applicable to the ldap server of XML database of the present invention, and the ldap database of ldap server is realized by the XML thesaurus.As shown in Figure 2, ldap server contains the LDAP front end, LDAP request processor, XQuery engine and LDAP answer processor.
LDAP front-end processing ldap protocol stack, its function comprises:
The LDAP request that-reception and decoding receive from interface I1;
-structural data of LDAP request is offered request processor by interface I2;
-by the structural data of interface I7 reception from the LDAP result of answer processor;
-LDAP result's structural data is encoded to the LDAP response and passes through interface I8 output.
The function of LDAP request processor comprises:
-convert the structural data of LDAP request to virtual XML file, and it is offered the XQuery engine by interface I3.Concrete, it is with script file or script name in the LDAP request, and Parameters Transformation offers the XQuery engine for the XML file.
The XQuery engine is based on engine XML database/store storehouse, commercial or that increase income, and its function comprises:
-script the name that provides according to the LDAP request processor obtains the script file that prestores and is written into by interface I4, perhaps is written into the script file that the LDAP request processor provides;
-carry out script file, by interface I5 operation XML database, obtain the operating result of XML form;
-by interface I6 the operating result of XML form is sent to answer processor;
The function of LDAP answer processor comprises:
-operating result of XML form is converted to the data structure that LDAP responds, and it is offered the LDAP front end by interface I7.
Wherein, interface I1 is the external interface that is used for the LDAP request, and interface I2 to I7 is inner API (application programming interfaces), and interface I8 is the external interface that is used for the LDAP response.
Fig. 3 is a module map that is applicable to the ldap server of non-XML database of the present invention.Its module much is similar to the module of ldap server shown in Figure 2, for example, and LDAP front end, LDAP request processor, XQuery engine, LDAP answer processor.The ldap server and the key distinction among Fig. 2 shown in Figure 3 are to be:
-ldap database is a non-XML database;
-XQuery engine is connected to the interface of ldap database by an inner api interface I5, and the XQuery engine is adjusted/expands to and utilizes interface I5 operation ldap database;
-this interface I5 with the access map of XPATH among the XQuery to visit, for example by the XPATH expression formula being converted to the one group of inner primitive that is used for database manipulation to real ldap database.
With a concrete instance the present invention is described below.
There is a ldap database in order, and it has following by the expressed archives of LDIF form.
The virtual XML database that is shone upon is:
Required database manipulation is to search the student who meets the following conditions in single LDAPSearch request:
If student name is studentName2, then return its teacher's name;
Otherwise, do not return any project.
This condition can't be expressed by a LDAP filtrator at the lane database of example.
Based on method of the present invention, can use following LDAPSearch to ask to carry out this database manipulation:
In this request, filtrator is empty, and return attribute also is empty, and promptly the complex logic of the operation of expression database is not indicated by the above information in the request with the attribute that returns.This complex logic and the attribute that returns all are placed in the LDAP control element in this LDAPSearch request, and be as follows:
Wherein, OID is that the control element of 1.2.3.4.5.6.7.8.9 is represented script, and its value is a script file itself; OID is the input parameter that the control element of 1.2.3.4.5.6.7.8.9.1 is represented script, and its value is studentName2.
Wherein, theing contents are as follows of xqueryExample1.xql:
This LDAPSearch request is mapped as virtual input xml file by the LDAP request processor, as described below:
The XQuery engine of ldap server is carried out the xqueryExample1.xql script with studentName2 as parameter, it is the student's of studentName2 teacher's DN and title that inquiry obtains name, and they are converted into LDAP SearchEntry response send to the LDAP client.
Certainly; the present invention also can have other various embodiments; under the situation that does not deviate from spirit of the present invention and essence thereof; those of ordinary skill in the art can make various corresponding changes and distortion according to the present invention, but these corresponding changes and distortion all should belong to the protection domain of the appended claim of the present invention.
One of ordinary skill in the art will appreciate that all or part of step in the said method can instruct related hardware to finish by program, described program can be stored in the computer-readable recording medium, as ROM (read-only memory), disk or CD etc.Alternatively, all or part of step of the foregoing description also can use one or more integrated circuit to realize.Correspondingly, each the module/unit in the foregoing description can adopt the form of hardware to realize, also can adopt the form of software function module to realize.The present invention is not restricted to the combination of the hardware and software of any particular form.
Claims (15)
1. a method that is used to have the database manipulation of complex logic in ldap server is characterized in that, comprises the steps:
I. receive the single LDAP request message from the LDAP client, contain the information relevant with script in this message, described script is used for by described server performed to carry out described database manipulation with complex logic;
Ii. obtain the described information relevant with script;
Iii. according to the described information relevant, obtain and carry out described script, to carry out described database manipulation with script;
Iv. the execution result with script returns to described LDAP client in the LDAP response message.
2. method according to claim 1 is characterized in that, the script reading database content of described complex logic, and/or change data-base content, and,
Described complex logic can't be expressed with the LDAP filtrator.
3. method according to claim 1 is characterized in that the described information relevant with script comprises the file of script, and described step I ii comprises:
-acquisition extracts the file of described script from described LDAP request message;
And/or,
Stored or be written into script on this ldap server, the described information relevant with script comprises the indication information of the script that indication has been stored or has been written on described ldap server, and described step I ii comprises:
-be written into the indicated script of indication information that stored, described, or selected loaded, the indicated script of described indication information.
4. method according to claim 1 is characterized in that, also contains the parameter of described database manipulation script in the described LDAP request message;
Described step I i also extracts described script argument from described LDAP request message;
Described step I ii also carries out described script according to described parameter.
5. method according to claim 4 is characterized in that, described information relevant with script and described parameter are placed in the corresponding LDAP control element in this LDAP request message,
From corresponding LDAP control element, extract described information relevant and described parameter among the described step I i respectively with script.
6. method according to claim 1 is characterized in that, when described script was the XQuery script, described step I comprised the steps:
-this LDAP request message receives and decodes;
-obtain the structural data in the LDAP request message, contain the described information relevant in this structural data with script;
Described step I i comprises the steps:
-extract the described information relevant with script, and be converted into the input parameter XML file of XQuery script, offer the XQuery query engine;
Described step I ii comprises the steps:
-this XQuery query engine obtains corresponding XQuery script and input parameter thereof;
-this XQuery query engine is carried out the XQuery script, ldap database is operated, and obtained the operating result of XML form;
Described step I v comprises:
-operating result of described XML form is converted to the data structure that LDAP responds;
-operating result of the data structure of LDAP response is encoded to the LDAP response message send it back the LDAP client.
7. method according to claim 6 is characterized in that, ldap database is expressed with virtual XML view, makes the XQuery script can operate virtual XML document, shines upon by a kind of general ldap directory inforamtion tree model and XSD model and finishes;
Wherein, this mapping principle all is suitable for all ldap databases;
The database bottom layer realization can be XML database or non-XML database, when ldap database right and wrong XML database, the XQuery interpreter will be finished the operation of virtual XML document by the application programming interface of actual database, with all will be mapped to the visit in True Data storehouse among the XQuery to the visit of XPATH.
8. method according to claim 1, wherein, described step I v is placed on the execution result of described script in the LDAP control element in the LDAP response message, and this LDAP response message is sent to the LDAP client.
9. method according to claim 1 is characterized in that this method also comprises the steps:
V. in carrying out described script, make a mistake/when unusual, with the described LDAP client of described script error/send it back unusually;
Described step v sends to the LDAP client with described script error/be placed on unusually in the LDAP control element in the LDAP response message with this LDAP response message.
10. one kind is used to ask ldap server to have the method for the database manipulation of complex logic in the LDAP client, it is characterized in that, comprises the steps:
I. the information relevant with script is placed in the single LDAP request message, described script is performed to carry out described database manipulation with complex logic by described server;
II. send this LDAP request message to described server;
III. receive execution result from the script in the LDAP response message of ldap server.
11. method according to claim 10 is characterized in that, wherein, and the script reading database content of described complex logic, and/or change data-base content,
Described complex logic can't be expressed with the LDAP filtrator.
12. method according to claim 10 is characterized in that, the described information relevant with script comprises following at least a:
The file of-script;
The indication information of the script that-indication has been stored on described ldap server or has been written into.
13. method according to claim 10 is characterized in that, described step I also comprises:
-parameter of described database manipulation script is placed in the LDAP request message;
Wherein, described step I is placed on the parameter of described information relevant with script and described database manipulation script in the LDAP control element in this LDAP request message.
14. method according to claim 10 is characterized in that, extracts the execution result of described script in the LDAP control element among the described Step II I from described LDAP response message.
15. method according to claim 10 is characterized in that, when described ldap server is carried out described script, produced wrong/unusual, this method is further comprising the steps of:
IV. receive from the script error in the LDAP response message of ldap server/unusual;
Wherein, extract described script error/unusual in the LDAP control element of described step IV from described LDAP response message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012100251551A CN103218378A (en) | 2012-01-19 | 2012-01-19 | Method for carrying out database operation based on complicated logic on basis of LDAP (lightweight directory access protocol) |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012100251551A CN103218378A (en) | 2012-01-19 | 2012-01-19 | Method for carrying out database operation based on complicated logic on basis of LDAP (lightweight directory access protocol) |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103218378A true CN103218378A (en) | 2013-07-24 |
Family
ID=48816177
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2012100251551A Pending CN103218378A (en) | 2012-01-19 | 2012-01-19 | Method for carrying out database operation based on complicated logic on basis of LDAP (lightweight directory access protocol) |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103218378A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101626365A (en) * | 2008-07-11 | 2010-01-13 | 中兴通讯股份有限公司 | Directory server and system and method for realizing LDAP extended operation |
| CN101685460A (en) * | 2008-09-23 | 2010-03-31 | 华为技术有限公司 | Database device, method and system for processing shared data |
| US20100250519A1 (en) * | 2009-03-24 | 2010-09-30 | Software Ag | XML database management system for an XML database comprising access protected XML data |
-
2012
- 2012-01-19 CN CN2012100251551A patent/CN103218378A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101626365A (en) * | 2008-07-11 | 2010-01-13 | 中兴通讯股份有限公司 | Directory server and system and method for realizing LDAP extended operation |
| CN101685460A (en) * | 2008-09-23 | 2010-03-31 | 华为技术有限公司 | Database device, method and system for processing shared data |
| US20100250519A1 (en) * | 2009-03-24 | 2010-09-30 | Software Ag | XML database management system for an XML database comprising access protected XML data |
Non-Patent Citations (1)
| Title |
|---|
| 崔志刚 等: "基于LDAP的XML数据访问", 《计算机应用研究》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6684222B1 (en) | Method and system for translating data associated with a relational database | |
| US7779386B2 (en) | Method and system to automatically regenerate software code | |
| US7072903B2 (en) | System and method for translating to and from hierarchical information systems | |
| CN1647080B (en) | Method and computer for accessing data in an environment of multiple data repositories | |
| CN102164050B (en) | Log parsing method and log parsing node device | |
| CN1318956C (en) | System and method for software component plug-in framework | |
| US8667508B2 (en) | Method for providing stand-in objects | |
| US20020049756A1 (en) | System and method for searching multiple disparate search engines | |
| CN106126540B (en) | Data base access system and its access method | |
| US7089533B2 (en) | Method and system for mapping between markup language document and an object model | |
| US20110153590A1 (en) | Apparatus and method for searching for open api and generating mashup block skeleton code | |
| WO2002019652A2 (en) | System and method for transmitting and retrieving data via a distributed persistence framework | |
| CN101421726A (en) | Occasionally-connected application server | |
| US20070185930A1 (en) | System, method and program product for adding, updating and removing RDF statements stored on a server | |
| US20080127056A1 (en) | Generation of managed assemblies for networks | |
| CN107145549B (en) | Database cache control method and system | |
| US6711734B1 (en) | Method for translating MOF metamodels to UML models | |
| US9600597B2 (en) | Processing structured documents stored in a database | |
| WO2000065486A2 (en) | A method of mapping semantic context to enable interoperability among disparate sources | |
| US6842905B2 (en) | Method and system for implementing collection program interface for accessing a collection of data associated with a legacy enumeration application interface | |
| EP1909170B1 (en) | Method and system for automatically generating a communication interface | |
| US7325003B2 (en) | Method and system for mapping datasources in a metadata model | |
| US20060095513A1 (en) | Hypermedia management system | |
| US6684386B1 (en) | Method for converting a UML rendering of an RSM-based metamodel to a UML rendering of MOF-based metamodel | |
| CN103218378A (en) | Method for carrying out database operation based on complicated logic on basis of LDAP (lightweight directory access protocol) |
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: 20130724 |