CN102253840A - Plugin management method and plugin manager - Google Patents
Plugin management method and plugin manager Download PDFInfo
- Publication number
- CN102253840A CN102253840A CN2011102224925A CN201110222492A CN102253840A CN 102253840 A CN102253840 A CN 102253840A CN 2011102224925 A CN2011102224925 A CN 2011102224925A CN 201110222492 A CN201110222492 A CN 201110222492A CN 102253840 A CN102253840 A CN 102253840A
- Authority
- CN
- China
- Prior art keywords
- plug
- unit
- plugin
- plugin manager
- calls
- 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.)
- Granted
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The invention provides a plugin management method and a plugin manager. The method comprises the following steps: establishing the plugin manager in an application program; establishing a plugin storage pool in the plugin manager; assigning a unique identifier to each plugin stored in the plugin storage pool; encapsulating each plugin, and providing a call interface for each plugin; encapsulating all plugins in the plugin storage pool into a plugin set; providing a call interface object of the plugin set to each plugin manager; when the application program needs to call a certain plugin, sending a call request to the plugin manager corresponding to the application program; calling the plugin set by the plugin manager through the call interface object; and searching for the plugin by the plugin set according to the identifier of the plugin needed to be called and returning the storage address of the plugin needed to be called. The plugin manager comprises an input/output module and is provided with a plugin storage pool and a plugin set call interface object communicating with the input/output module. According to the invention, flexible call of the plugins can be realized, and the development efficiency of collaboration software is improved.
Description
Technical field
The present invention relates to the develop computer software field, relate in particular to a kind of plug-in management method and plugin manager of computing machine.
Background technology
Development along with the develop computer software technology, people are when development computer software, usually in application program, reserve the calling interface of some, so that the application program run duration calls required plug-in unit by these calling interfaces, to realize various functions neatly.The program development personnel design relevant plug-in unit usually when developing application.
In order to manage the employed plug-in unit of application program, plugin manager is set during the existing application program development mostly, each application program manages a plurality of plug-in units by the plugin manager of establishing certainly, mainly is that plug-in unit is called.The employed a part of plug-in unit of application program, as the plug-in unit of this application-specific, can develop in the lump with application program, and usually and application program be stored in the lump in the specified memory territory.And can then be stored in usually in the common area of an appointment for the public plug-in unit of a plurality of application calls, each application program need be called custom plug-in or public plug-in unit by plugin manager.No matter be custom plug-in or public plug-in unit, all be endowed unique identification number during each developing plug, and all write characteristic description, be used to describe the function that this plug-in unit is realized.
The calling of plug-in unit is to use calling interface to realize that calling interface provides the memory address of plug-in unit, realizes calling of plug-in unit by application program according to memory address redirect and the instruction carried out in the plug-in unit memory address.When calling plug-in unit, plugin manager is searched needed plug-in unit according to the identification number or the characteristic description of plug-in unit.
The employed plug-in unit of existing application must be the plug-in unit through registering in the plugin manager of this application program, therefore, if a public plug-in unit can be by a plurality of application calls, at first need in a plurality of application programs, register, can't be employed program without the plug-in unit of plugin manager registration and call.
Be provided with input/output module in the plugin manager, be used to receive the call request that application program is sent, also be provided with the calling interface of a plurality of plug-in units of having registered, after receiving call request, according to call request information searching corresponding insert, and the memory address of the plug-in unit that finds is returned application program by input/output module, carry out dependent instruction by the application program redirect.
But, because the plugin manager of each application program all works alone, the plug-in unit of having registered can only be searched and call to the plugin manager of each application program in this plugin manager, the plug-in unit that its plugin manager that can't call other application programs in the same system has existed and registered.For example, the plugin manager A1 of application A can call chartered plug-in unit A2, A3, and the plugin manager B1 of Another Application program B can call chartered plug-in unit B2, B3.When application A needed application plug-in B2 to realize a certain function, owing to plug-in unit B2 registers at plugin manager A1, so plugin manager A1 can't call plug-in unit B2.Like this, bring great inconvenience for the management and the use of plug-in unit, also cause the overlapping development of plug-in unit easily, cause computer system files too huge.In the synergic software development process, also often run into similar problem, cause the development amount big, inefficiency.
Summary of the invention
Fundamental purpose of the present invention provides a kind of plug-in management method that plug-in unit is called by different plugin manager of being convenient to.
Another object of the present invention provides a kind of plug-in management method that improves synergic software development efficient.
A kind of plugin manager that helps developing plug is provided on a further object of the present invention.
In order to realize above-mentioned fundamental purpose, plug-in management method provided by the invention is included in each application program and sets up plugin manager, at the built-in vertical cutting spare storage pool of plugin manager, give unique identification number for each plug-in unit that is stored in the plug-in unit storage pool, and encapsulate each plug-in unit, for each plug-in unit provides calling interface correspondingly, all plug-in units in all plug-in unit storage pools are packaged into plug set, the calling interface object of plug set is provided to each plugin manager, when application program need be called a certain plug-in unit, plugin manager to the application program correspondence is sent call request, plugin manager is by calling interface object reference plug set, and plug set is searched the required plug-in unit that calls according to the identification number of the required plug-in unit that calls and returned the memory address of the required plug-in unit that calls.
By such scheme as seen, the plug-in unit that all application programs can be called is packaged into plug set, arbitrary plugin manager all can be invoked at intrasystem arbitrary plug-in unit, whether the use of plug-in unit is not subjected to the restriction in this plugin manager registration, as long as this plug-in unit can be called shortly at Installed System Memory.Like this, make things convenient for the use of plug-in unit, and when synergic software development, can improve the development efficiency of collaboration software greatly, avoided the plug-in unit overlapping development of similar functions.
A preferred scheme is, plugin manager judges whether the required plug-in unit that calls is registered, if not registration is then registered operation to the required plug-in unit that calls before finding and returning memory address behind the required plug-in unit that calls in plugin manager.
This shows that when the application call plug-in unit, plugin manager can be registered operation to unregistered plug-in unit, and after the registration operation, return the memory address of plug-in unit.Like this, even the plug-in unit of application call is not registered in the plugin manager of this application program in advance, plugin manager still can be registered and call plug-in unit immediately, realizes the flexible management of plug-in unit.
For realizing an above-mentioned purpose again, plugin manager provided by the invention comprises input/output module; And be provided with the plug-in unit storage pool, and plug-in unit storage pool internal memory contains at least one plug-in unit, and each plug-in unit has unique identification number, and is provided with a plurality of plug-in units calling interface one to one in the plug-in unit storage pool; Also be provided with the plug set calling interface object that communicates with input/output module, plug set is formed by a plurality of plug-in unit encapsulation in a plurality of plug-in unit storage pools, plugin manager can be passed through the calling interface object reference plug set of plug set, and searches and call the required plug-in unit that calls by plug set.
By such scheme as seen, by all plug-in units are packaged into plug set, and the plugin manager of each application program all can be called arbitrary plug-in unit by the calling interface object, can avoid the overlapping development of plug-in unit when synergic software development, promotes efficiency of software.
A preferred scheme is, plugin manager also comprises the plug-in registration module that communicates with plug-in unit storage pool and calling interface object, is used for need calling and unregistered plug-in unit is registered operation plugin manager.
This shows, by the plug-in registration module plug-in unit is registered, help plugin manager plug-in unit is managed, simultaneously also can be by the legitimacy of registration operation demonstration plug-in unit, avoid the illegal plug-in unit of application call and influence the work of application program.
Description of drawings
Fig. 1 is a process flow diagram of setting up plug set among the plug-in management method embodiment of the present invention.
Fig. 2 is the process flow diagram that plug-in unit uses among the plug-in management method embodiment of the present invention.
Fig. 3 is the process flow diagram of plug-in registration among the plug-in management method embodiment of the present invention.
Fig. 4 is the structured flowchart of plugin manager embodiment of the present invention.
The invention will be further described below in conjunction with drawings and Examples.
Embodiment
Plug-in management method of the present invention is applicable to develop computer software and use occasion, is particularly useful for object-oriented programming.When using plug-in management method of the present invention and carrying out software development, the developer should reserve a plurality of ports in application program, so that can call various plug-in units neatly to realize corresponding function, as realizing picture decoding function etc. during the application program operation.
Referring to Fig. 1, during developing application, at first plugin manager, i.e. execution in step S1 need be set in application program.Need to prove, each application program in the system is equipped with the plugin manager of oneself, and the plugin manager of each application program all works alone, not influenced by the plugin manager of other application programs, the information that does not also receive other application programs and sent, each plugin manager can only receive the information of the application program that this plugin manager is set, also can only be to this application program return message.
The plug-in unit storage pool is set in plugin manager, and as shown in Figure 4, plug-in unit storage pool 10 internal memories contain a plurality of plug-in units 11,12 ... N, each plug-in unit all can be realized specific function, as Show Picture, audio decoder etc.All be encapsulated in behind each developing plug in the plugin manager of an application program, therefore, intrasystem plug-in unit quantity is fixed, after system development finishes, do not accept the plug-in unit that increases newly, only accept the upgrade file of plug-in unit, be that plug-in unit can only be updated, can not increase the quantity of plug-in unit.And each plug-in unit is equipped with calling interface, is used to be employed program and calls.Certainly, each plug-in unit is equipped with the characteristic description of oneself, be used to describe this plug-in unit the function that can realize so that application identification and calling.
In step S2, need to give each plug-in unit to give unique identification number, be used to identify each plug-in unit.Said herein unique identification number is meant that the identification number of each plug-in unit all is unique, and is not only to be unique in the system that the developer develops in application program.Therefore, different application programs also can be discerned each plug-in unit uniquely according to the identification number of plug-in unit.Certainly, the identification number of plug-in unit should be given each plug-in unit when application program and corresponding developing plug, in the developing application process, can set in advance the required plug-in unit that calls, like this, the plug-in unit of specific identifier number the time can be directly called in the application program operation, thereby improves the efficient of calling of plug-in unit.
After all application developments finish, intrasystem all plug-in units are also correspondingly developed and are finished, at this moment, execution in step S3, all plug-in units in all plugin manager are packaged into plug set, plug set can be by the mode of data structure body definition all plug-in units to be organized, and the calling interface of plug set is set, and is defined as the calling interface object.
At last, execution in step S4 provides the calling interface object of plug set to the plugin manager of each application program, all towards the calling interface object, calls concrete plug-in unit by the calling interface object when each plugin manager need be called plug-in unit.
As shown in Figure 4, in plugin manager, calling interface object 30 can be towards the calling interface 21,22 of each plug-in unit ... M, promptly plugin manager can be called arbitrary intrasystem plug-in unit that is present in by calling interface object 30.
Be provided with input/output module 31 in the plugin manager, can receive the call request information that application program is sent, and call request information is sent to calling interface object 30, carry out corresponding insert by calling interface object 30 and call work.And, during to the application program return message, the information of returning is sent to application program by input/output module 31 at calling interface object 30.
And, also be provided with the plug-in registration module 35 that can communicate with plug-in unit storage pool 10, calling interface object 30 in the plugin manager, be used for plug-in unit is registered operation, the registration operation of plug-in unit will be in subsequent detailed description.
Referring to Fig. 2, in the application program operational process, in the time of need calling a certain plug-in unit, execution in step S11 at first, the known required identification number that calls plug-in unit of application program sends call request to plugin manager, if then can directly be sent to plugin manager with the required identification number that calls plug-in unit in the lump, if the unknown required identification number that calls plug-in unit of application program then sends required description of calling function that plug-in unit is realized.
After plugin manager received call request, execution in step S12 called plug set, and this moment, plugin manager was not directly called concrete plug-in unit, and therefore, plugin manager is directly in the face of calling interface object 30.After calling interface object 30 receives call request information, according to the required concrete plug-in unit that calls of the content search of call request information, i.e. execution in step S13.
If comprised the identification number of the plug-in unit that is called in the call request information that application program is sent, calling interface object 30 directly finds out concrete plug-in unit according to identification number, if do not comprise the identification number of required plug-in unit in the call request information that application program is sent, then calling interface object 30 finds out the identification number of suitable inserts according to the characteristic description of each plug-in unit, finds out corresponding insert according to identification number again.
Then, plugin manager judges whether the plug-in unit that is found is registered in this plugin manager, be execution in step S14, if register, execution in step S15 then, calling interface object 30 returns the required memory address of calling plug-in unit by input/output module 31 to application program, and application program directly jumps to this address and carries out corresponding instruction according to this memory address, thereby realizes calling of plug-in unit.Certainly, if the required plug-in unit that calls is to set in advance in application development in plug-in unit storage pool 10, then this plug-in unit is registered in plugin manager, and promptly plug-in unit is in plug-in unit storage pool 10 memory allocated spaces, and is called for calling interface object 30 by the calling interface of correspondence.
If the required plug-in unit that calls is not registered in plugin manager, plugin manager execution in step S16 registers operation to unregistered plug-in unit, and at registration operation back execution in step S15, the memory address of plug-in unit is returned application program.
Because plug set is to be formed by all plug-in unit encapsulation in the system, as long as the required plug-in unit that calls is present in the system, arbitrary plugin manager all can realize calling this plug-in unit.And, when plugin manager is called unregistered plug-in unit, can directly register operation, and after the registration operation, the required memory address of calling plug-in unit be returned plug-in unit.
Referring to Fig. 3, when needing registered plug-ins, execution in step S21 at first, whether the plug-in unit of judging required registration is present in the plug-in unit storage pool, if Already in the plug-in unit storage pool, then finish the plug-in registration operation, if be not present in the plug-in unit storage pool, then execution in step S22 judges further whether the plug-in unit of required registration is legal plug-in unit.Said herein legal plug-in unit is meant that plug-in unit is developed by system development side, and plug-in unit with specific function, if plug-in unit is developed by system development side, think that then this plug-in unit is illegal plug-in unit, do not allow this plug-in registration, be legal plug-in unit with this plug-in unit of guaranteeing that application program is called, guarantee the security of application program operation.
If it is not legal plug-in unit that plugin manager judge to need the plug-in unit of registration, then finish the registration operation, promptly illegal plug-in unit can not be by registration, guarantees that application program can not call illegal plug-in unit.If plugin manager judges that needing the plug-in unit of registration is legal plug-in unit, then execution in step S23 to the plug-in unit allocation space of new registration, is provided with calling interface just for the plug-in unit of new registration in the plug-in unit storage pool in storage pool, is called by the calling interface object.
Certainly, because plug-in unit can bring in constant renewal in, the plug-in unit after the renewal continues to continue to use original identification number and characteristic description, and calling interface object 30 still can find plug-in unit after the renewal by identification number.Whether need to re-register as for the plug-in unit after upgrading, determine by the actual conditions of system development.
Because calling interface object all plug-in units in can system-oriented, but be not that all plug-in units all are stored in the plug-in unit storage pool, therefore the calling interface of a certain plug-in unit can appear having in the plug-in unit storage pool, but the situation that does not have the entity program of this plug-in unit, the memory address of calling interface object by plug-in unit is provided jumped to the memory address of this plug-in unit and carried out relevant instruction by application program to application program.
As seen, by plug set all plug-in units in the system are carried out unified management, can allow the intrasystem arbitrary legal plug-in unit of arbitrary application call, avoid intrasystem plug-in unit can not be employed the problem of routine call, in the synergic software development process, can realize sharing of plug-in unit, avoid the plug-in unit overlapping development, improve the development efficiency of collaboration software.
Certainly, the foregoing description only is a preferred implementation of the present invention, during practical application, more change can also be arranged, for example, in non-open system,, can exempt the step of plug-in registration because the user can not install new plug-in unit, be plugin manager as long as in the discovery system corresponding insert is arranged, can call this plug-in unit voluntarily, no matter this plug-in unit whether register by process, such change also can realize purpose of the present invention.
It is emphasized that at last to the invention is not restricted to above-mentioned embodiment, also should be included in the protection domain of claim of the present invention as the variations such as change of the concrete steps of the change of plug set packing forms, plug-in registration.
Claims (5)
1. plug-in management method comprises
In each application program, set up plugin manager;
It is characterized in that:
At the built-in vertical cutting spare storage pool of described plugin manager, give unique identification number for each plug-in unit that is stored in the described plug-in unit storage pool, and encapsulate each described plug-in unit, for each described plug-in unit provides calling interface correspondingly;
All plug-in units in all described plug-in unit storage pools are packaged into plug set, the calling interface object of described plug set is provided to each described plugin manager;
When described application program need be called a certain plug-in unit, plugin manager to described application program correspondence is sent call request, described plugin manager is by the described plug set of described calling interface object reference, and described plug set is searched the required plug-in unit that calls according to the identification number of the required plug-in unit that calls and returned the memory address of the required plug-in unit that calls.
2. plug-in management method according to claim 1 is characterized in that:
Described plugin manager judges whether the required plug-in unit that calls is registered before finding and returning memory address behind the required plug-in unit that calls in described plugin manager, if not registration is then registered operation to the required plug-in unit that calls.
3. plug-in management method according to claim 2 is characterized in that:
Described registration operation comprises that described plugin manager judges that the required plug-in unit that calls is whether in the plug-in unit storage pool of Already in described plugin manager correspondence, if do not have, then after judging that the required plug-in unit that calls is legal plug-in unit, in described plug-in unit storage pool, give required plug-in unit memory allocated space of calling.
4. plugin manager comprises
Input/output module;
It is characterized in that:
The plug-in unit storage pool, described plug-in unit storage pool internal memory contains at least one plug-in unit, and each described plug-in unit has unique identification number, and is provided with described plug-in unit calling interface one to one in the described plug-in unit storage pool;
The calling interface object of plug set, communicate with described input/output module, and described plug set is formed by a plurality of described plug-in unit encapsulation in a plurality of described plug-in unit storage pools, described plugin manager can be passed through the described plug set of calling interface object reference of described plug set, and searches and call the required plug-in unit that calls by described plug set.
5. plugin manager according to claim 4 is characterized in that:
Also comprise the plug-in registration module, communicate, and described plug-in registration module is used for need calling and unregistered plug-in unit is registered operation described plugin manager with described plug-in unit storage pool and described calling interface object.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011102224925A CN102253840B (en) | 2011-08-04 | 2011-08-04 | Plugin management method and plugin manager |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011102224925A CN102253840B (en) | 2011-08-04 | 2011-08-04 | Plugin management method and plugin manager |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102253840A true CN102253840A (en) | 2011-11-23 |
| CN102253840B CN102253840B (en) | 2013-11-13 |
Family
ID=44981120
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2011102224925A Active CN102253840B (en) | 2011-08-04 | 2011-08-04 | Plugin management method and plugin manager |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102253840B (en) |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102685220A (en) * | 2012-04-28 | 2012-09-19 | 苏州阔地网络科技有限公司 | Method and system for data interaction based on WEB page |
| CN102938037A (en) * | 2012-11-26 | 2013-02-20 | 北京奇虎科技有限公司 | Plug-in calling method and plug-in manager for browser |
| WO2013135133A1 (en) * | 2012-03-16 | 2013-09-19 | 腾讯科技（深圳）有限公司 | Method, apparatus and computer storage medium for plug-in management and control |
| CN103365674A (en) * | 2012-03-31 | 2013-10-23 | 腾讯科技（深圳）有限公司 | Plug-in management method, device and system based on mobile terminal |
| CN103473073A (en) * | 2013-09-25 | 2013-12-25 | 张新杰 | Method and system for fast calling out command calling interface |
| CN103544013A (en) * | 2013-10-25 | 2014-01-29 | 优视科技有限公司 | Plug-in system and plug-in management method |
| CN103544039A (en) * | 2013-10-30 | 2014-01-29 | 北京国双科技有限公司 | Plug-in loading processing method and device |
| CN103593191A (en) * | 2013-11-19 | 2014-02-19 | 乐视致新电子科技（天津）有限公司 | Method and device for calling application program data |
| CN104168136A (en) * | 2014-08-08 | 2014-11-26 | 小米科技有限责任公司 | Informing method and device for connecting condition between external device and router |
| CN104301916A (en) * | 2014-11-07 | 2015-01-21 | 东南大学 | Test and optimization method, device and system based on universal mobile intelligent terminal plug-in connector |
| CN104932887A (en) * | 2015-06-12 | 2015-09-23 | 北京京东尚科信息技术有限公司 | Plug-in management method of platform system and platform system |
| CN105095694A (en) * | 2014-05-14 | 2015-11-25 | 腾讯科技（深圳）有限公司 | Method and system for calling plug-ins by webpages |
| CN105373396A (en) * | 2015-08-14 | 2016-03-02 | 腾讯科技（深圳）有限公司 | Method and device for updating plug-in in plug-in platform |
| US9798827B2 (en) | 2013-10-25 | 2017-10-24 | Uc Mobile Co., Ltd. | Methods and devices for preloading webpages |
| CN107315628A (en) * | 2017-06-13 | 2017-11-03 | 浪潮金融信息技术有限公司 | Plug-in unit call method and device, computer-readable recording medium, terminal |
| CN107493336A (en) * | 2017-08-21 | 2017-12-19 | 北京北信源软件股份有限公司 | Realize method and apparatus, computer-readable recording medium and the storage control of client plug-in |
| CN108388453A (en) * | 2018-01-15 | 2018-08-10 | 珠海格力电器股份有限公司 | Plug-in management method, application program forming method, device and server |
| CN108984224A (en) * | 2018-06-13 | 2018-12-11 | 中国平安人寿保险股份有限公司 | A kind of plug-in management method, computer readable storage medium and terminal device |
| CN110673844A (en) * | 2019-09-26 | 2020-01-10 | 苏州中科全象智能科技有限公司 | Image processing software development method and system |
| CN111400054A (en) * | 2018-12-27 | 2020-07-10 | 浙江大学 | Network plug-in calling method and device, computer storage medium and electronic equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1553332A (en) * | 2003-06-02 | 2004-12-08 | 联想(北京)有限公司 | Facility centralizing management method based by plugging technology |
| US20080295074A1 (en) * | 2007-05-25 | 2008-11-27 | Schneider James P | Data management interface with configurable plugins |
| CN101571809A (en) * | 2009-05-14 | 2009-11-04 | 阿里巴巴集团控股有限公司 | Implementation method of plug-in registration and device thereof |
| CN101699405A (en) * | 2009-10-26 | 2010-04-28 | 中兴通讯股份有限公司 | Method and device for interaction between host program and plug-in and interaction between plug-ins |
| CN101950255A (en) * | 2010-09-16 | 2011-01-19 | 深圳市迎风传讯科技有限公司 | Plug-in management method, plug-in manager and set top box |
-
2011
- 2011-08-04 CN CN2011102224925A patent/CN102253840B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1553332A (en) * | 2003-06-02 | 2004-12-08 | 联想(北京)有限公司 | Facility centralizing management method based by plugging technology |
| US20080295074A1 (en) * | 2007-05-25 | 2008-11-27 | Schneider James P | Data management interface with configurable plugins |
| CN101571809A (en) * | 2009-05-14 | 2009-11-04 | 阿里巴巴集团控股有限公司 | Implementation method of plug-in registration and device thereof |
| CN101699405A (en) * | 2009-10-26 | 2010-04-28 | 中兴通讯股份有限公司 | Method and device for interaction between host program and plug-in and interaction between plug-ins |
| CN101950255A (en) * | 2010-09-16 | 2011-01-19 | 深圳市迎风传讯科技有限公司 | Plug-in management method, plug-in manager and set top box |
Cited By (30)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2013135133A1 (en) * | 2012-03-16 | 2013-09-19 | 腾讯科技（深圳）有限公司 | Method, apparatus and computer storage medium for plug-in management and control |
| US9396005B2 (en) | 2012-03-16 | 2016-07-19 | Tencent Technology (Shenzhen) Company Limited | Method, apparatus and computer storage medium for plug-in management and control |
| CN103365674A (en) * | 2012-03-31 | 2013-10-23 | 腾讯科技（深圳）有限公司 | Plug-in management method, device and system based on mobile terminal |
| CN102685220A (en) * | 2012-04-28 | 2012-09-19 | 苏州阔地网络科技有限公司 | Method and system for data interaction based on WEB page |
| CN102938037B (en) * | 2012-11-26 | 2016-06-29 | 北京奇虎科技有限公司 | A kind of plug-in unit call method for browser and plugin manager |
| CN102938037A (en) * | 2012-11-26 | 2013-02-20 | 北京奇虎科技有限公司 | Plug-in calling method and plug-in manager for browser |
| CN103473073A (en) * | 2013-09-25 | 2013-12-25 | 张新杰 | Method and system for fast calling out command calling interface |
| CN103544013A (en) * | 2013-10-25 | 2014-01-29 | 优视科技有限公司 | Plug-in system and plug-in management method |
| US10489476B2 (en) | 2013-10-25 | 2019-11-26 | Uc Mobile Co., Ltd. | Methods and devices for preloading webpages |
| US9798827B2 (en) | 2013-10-25 | 2017-10-24 | Uc Mobile Co., Ltd. | Methods and devices for preloading webpages |
| CN103544013B (en) * | 2013-10-25 | 2017-06-06 | 优视科技有限公司 | A kind of plug-in system and plug-in management method |
| CN103544039A (en) * | 2013-10-30 | 2014-01-29 | 北京国双科技有限公司 | Plug-in loading processing method and device |
| CN103593191A (en) * | 2013-11-19 | 2014-02-19 | 乐视致新电子科技（天津）有限公司 | Method and device for calling application program data |
| CN105095694B (en) * | 2014-05-14 | 2019-04-12 | 腾讯科技（深圳）有限公司 | The method and system of webpage calling plug-in unit |
| CN105095694A (en) * | 2014-05-14 | 2015-11-25 | 腾讯科技（深圳）有限公司 | Method and system for calling plug-ins by webpages |
| CN104168136A (en) * | 2014-08-08 | 2014-11-26 | 小米科技有限责任公司 | Informing method and device for connecting condition between external device and router |
| CN104168136B (en) * | 2014-08-08 | 2018-04-06 | 小米科技有限责任公司 | The Notification Method and device of connection between external equipment and router |
| CN104301916A (en) * | 2014-11-07 | 2015-01-21 | 东南大学 | Test and optimization method, device and system based on universal mobile intelligent terminal plug-in connector |
| CN104301916B (en) * | 2014-11-07 | 2018-01-02 | 东南大学 | Test optimization method, apparatus and system based on mobile intelligent terminal universal card |
| CN104932887A (en) * | 2015-06-12 | 2015-09-23 | 北京京东尚科信息技术有限公司 | Plug-in management method of platform system and platform system |
| CN104932887B (en) * | 2015-06-12 | 2018-02-02 | 北京京东尚科信息技术有限公司 | The plug-in management method and plateform system of a kind of plateform system |
| CN105373396A (en) * | 2015-08-14 | 2016-03-02 | 腾讯科技（深圳）有限公司 | Method and device for updating plug-in in plug-in platform |
| CN107315628A (en) * | 2017-06-13 | 2017-11-03 | 浪潮金融信息技术有限公司 | Plug-in unit call method and device, computer-readable recording medium, terminal |
| CN107315628B (en) * | 2017-06-13 | 2020-11-17 | 浪潮金融信息技术有限公司 | Plug-in calling method and device, computer readable storage medium and terminal |
| CN107493336A (en) * | 2017-08-21 | 2017-12-19 | 北京北信源软件股份有限公司 | Realize method and apparatus, computer-readable recording medium and the storage control of client plug-in |
| CN108388453A (en) * | 2018-01-15 | 2018-08-10 | 珠海格力电器股份有限公司 | Plug-in management method, application program forming method, device and server |
| CN108984224A (en) * | 2018-06-13 | 2018-12-11 | 中国平安人寿保险股份有限公司 | A kind of plug-in management method, computer readable storage medium and terminal device |
| CN111400054A (en) * | 2018-12-27 | 2020-07-10 | 浙江大学 | Network plug-in calling method and device, computer storage medium and electronic equipment |
| CN111400054B (en) * | 2018-12-27 | 2024-03-08 | 浙江大学 | Network plug-in calling method and device, computer storage medium and electronic equipment |
| CN110673844A (en) * | 2019-09-26 | 2020-01-10 | 苏州中科全象智能科技有限公司 | Image processing software development method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102253840B (en) | 2013-11-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102253840B (en) | Plugin management method and plugin manager | |
| CA3154919C (en) | Data object identification generating method, device, computer equipment and storage medium | |
| CN109144478B (en) | Component frame system and method of using the same | |
| US20090031402A1 (en) | Method and apparatus for managing access privilege in cldc osgi environment | |
| US20140201822A1 (en) | Method and system for permitting access to resources based on instructions of a code tagged with an identifier assigned to a domain | |
| US7305376B2 (en) | Multiple language-dependent resources compacted into a single resource file | |
| US20180307498A1 (en) | Driver Loading Method and Server | |
| CN112073448B (en) | Service isolation method and device for dual-system terminal | |
| CN112068968B (en) | Service access method and device for dual-system terminal | |
| EP3072318A1 (en) | Profile integration management | |
| CN106569880A (en) | Method and system for dynamically sharing resources between Android applications | |
| US20120227056A1 (en) | Method and system for enabling access to functionality provided by resources outside of an operating system environment | |
| CN109347716B (en) | Instantiation method and device of consumer VNF | |
| CN115086166A (en) | Computing system, container network configuration method, and storage medium | |
| CN109347661B (en) | Instantiation method and device of consumer VNF | |
| US20100299652A1 (en) | Apparatus and method for managing components in sca system | |
| CN105677481A (en) | Method and system for processing data and electronic equipment | |
| CN103186386A (en) | Application loading method and system | |
| US20200034156A1 (en) | Resource Optimization and Reuse in Resource Constrained Environment | |
| CN102170428A (en) | Dynamic expansion management method of isomerous virtual machine platform | |
| CN114710350A (en) | Allocation method and device for callable resources | |
| CN106778270A (en) | The detection method and system of a kind of malicious application | |
| CN113282541A (en) | File calling method and device and electronic equipment | |
| CN108804236B (en) | AIDL file sharing method and system | |
| CN113504872A (en) | Method, system, equipment and medium for mounting virtual disk on cloud physical machine |
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 |