CN102253840B - Plugin management method and plugin manager - Google Patents
Plugin management method and plugin manager Download PDFInfo
- Publication number
- CN102253840B CN102253840B CN2011102224925A CN201110222492A CN102253840B CN 102253840 B CN102253840 B CN 102253840B CN 2011102224925 A CN2011102224925 A CN 2011102224925A CN 201110222492 A CN201110222492 A CN 201110222492A CN 102253840 B CN102253840 B CN 102253840B
- 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.)
- Active
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 develop computer software, usually reserve the calling interface of some in application program, so that the application program run duration calls required plug-in unit by these calling interfaces, to realize neatly various functions.The program development personnel design relevant plug-in unit usually when developing application.
The plug-in unit that uses in order to manage application program, arrange plugin manager mostly during existing application development, each application program manages a plurality of plug-in units by the plugin manager of certainly establishing, and is mainly that plug-in unit is called.A part of plug-in unit that application program is used, 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 storage area of appointment.And can usually be stored in the common area of an appointment for the public plug-in unit of a plurality of application calls, each application program need to 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 for describing the function that this plug-in unit is realized.
Calling of plug-in unit is to use calling interface to realize, calling interface provides the memory address of plug-in unit, by application program, according to memory address redirect and the instruction carried out in the plug-in unit memory address, realizes calling of plug-in unit.While calling plug-in unit, plugin manager is searched needed plug-in unit according to identification number or the characteristic description of plug-in unit.
The plug-in unit that existing application is used 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 to register in a plurality of application programs, can't be employed program without the plug-in unit of plugin manager registration and call.
Be provided with input/output module in plugin manager, be used for receiving the call request that application program is sent, also be provided with the calling interface of a plurality of chartered plug-in units, after receiving call request, plug-in unit corresponding according to the call request information searching, and the memory address of the plug-in unit that will find by input/output module returns to application program, by the application program redirect, carries out dependent instruction.
But, because the plugin manager of each application program all works alone, the plug-in unit of having registered in this plugin manager can only be searched and call to the plugin manager of each application program, the plug-in unit that its plugin manager that can't call other application programs in 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, because plug-in unit B2 does not register at plugin manager A1, so plugin manager A1 can't call plug-in unit B2.Like this, bring great inconvenience for the management and using of plug-in unit, also easily cause the overlapping development of plug-in unit, cause computer system files too huge.Also often run into Similar Problems in the synergic software development process, cause the development amount large, inefficiency.
Summary of the invention
Fundamental purpose of the present invention is to provide 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 is to provide a kind of plug-in management method that improves synergic software development efficiency.
A kind of plugin manager that is conducive to 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 to be called a certain plug-in unit, send call request to the plugin manager that application program is corresponding, plugin manager is by calling interface object reference plug set, 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 is returned to 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, the use of plug-in unit is not subjected to the restriction of whether in this plugin manager, having registered, as long as this plug-in unit can be called shortly at Installed System Memory.Like this, facilitate the use of plug-in unit, and when synergic software development, can greatly improve the development efficiency of collaboration software, 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 in plugin manager, if not registration is registered operation to the required plug-in unit that calls before finding after the required plug-in unit that calls and returning to memory address.
This shows, when the application call plug-in unit, plugin manager can be registered operation to unregistered plug-in unit, and returns to the memory address of plug-in unit after the registration operation.Like this, even the plug-in unit of application call is not registered in advance in the plugin manager of this application program, 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 storing at least one plug-in unit in the plug-in unit storage pool, 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 by plug set, searches and call the required plug-in unit that calls.
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 the efficiency of software development.
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 to calling and unregistered plug-in unit is registered operation plugin manager.
This shows, by the plug-in registration module, plug-in unit is registered, be conducive to 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 affect the work of application program.
Description of drawings
Fig. 1 sets up the process flow diagram of plug set in plug-in management method embodiment of the present invention.
Fig. 2 is the process flow diagram that in plug-in management method embodiment of the present invention, plug-in unit uses.
Fig. 3 is the process flow diagram of plug-in registration in 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 applying plug-in management method of the present invention and carrying out software development, the developer should reserve a plurality of ports in application program, in order to can call neatly various plug-in units to realize corresponding function during the application program operation, as realizes picture decoding function etc.
Referring to Fig. 1, during developing application, at first plugin manager need to be set in application program, namely perform step S1.Need to prove, each application program in system is equipped with the plugin manager of oneself, and the plugin manager of each application program all works alone, not affected by the plugin manager of other application programs, do not receive the information that other application programs send yet, 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, as shown in Figure 4, stores a plurality of plug-in units 11,12 in plug-in unit storage pool 10 ... N, each plug-in unit all can be realized specific function, as Show Picture, audio decoder etc.All be encapsulated in after each developing plug in the plugin manager of an application program, therefore, intrasystem plug-in unit quantity is fixed, after system development is complete, 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 for being employed program and calls.Certainly, each plug-in unit is equipped with the characteristic description of oneself, be used for to describe the function that this plug-in unit can be realized, so that application identification and calling.
In step S2, need to give unique identification number to each plug-in unit, be used for each plug-in unit of sign.Said unique identification number herein, refer to that in system that the developer develops, the identification number of each plug-in unit is all unique, and is not only to be unique in application program.Therefore, different application programs also can be identified 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, in application program when operation, can directly be called the plug-in unit of specific identifier number, thereby improve the efficiency of calling of plug-in unit.
After all application developments are complete, intrasystem all plug-in units are also correspondingly developed complete, at this moment, execution 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.
Finally, perform step S4, the calling interface object of plug set is provided to the plugin manager of each application program,, all towards the calling interface object, by the calling interface object, call concrete plug-in unit when each plugin manager need to 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, namely 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 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 plug-in unit by calling interface object 30 and call work.And, at calling interface object 30, during to the application program return message, the information exchange that returns is crossed input/output module 31 is sent to application program.
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 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 to calling a certain plug-in unit, at first perform step S11, the known required identification number that calls plug-in unit of application program sends call request to plugin manager, if 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, send required description of calling the plug-in unit realization of functions.
After plugin manager received call request, execution 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 received call request information, the concrete plug-in unit that call required according to the content search of call request information, namely performed 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, calling interface object 30 finds out the identification number of suitable inserts according to the characteristic description of each plug-in unit, then according to identification number, finds out corresponding plug-in unit.
Then, whether the plug-in unit that the plugin manager judgement finds is registered in this plugin manager, namely perform step S14, if register, perform step S15, calling interface object 30 returns to 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, this plug-in unit is registered in plugin manager, and namely plug-in unit is in plug-in unit storage pool 10 memory allocated spaces, and by the calling interface of correspondence, for calling interface object 30, is called.
If the required plug-in unit that calls is not registered in plugin manager, plugin manager execution step S16, register operation to unregistered plug-in unit, and perform step S15 after the registration operation, and the memory address of plug-in unit is returned to application program.
Because plug set is to be formed by all plug-in unit encapsulation in system, as long as the required plug-in unit that calls is present in system, arbitrary plugin manager all can realize calling this plug-in unit.And, when plugin manager is called unregistered plug-in unit, can directly to plug-in unit, register operation, and after the registration operation, the required memory address of calling plug-in unit be returned.
Referring to Fig. 3, while needing registered plug-ins, at first perform step S21, whether the plug-in unit that judges required registration is present in the plug-in unit storage pool, if Already in the plug-in unit storage pool, finish the plug-in registration operation, if be not present in the plug-in unit storage pool, perform step S22, judge further whether the required plug-in unit of registering is legal plug-in unit.Said legal plug-in unit refers to that plug-in unit is developed by system development side herein, and the plug-in unit with specific function, if plug-in unit is not developed by system development side, think that 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 judgement needs the plug-in unit of registration, finish the registration operation, namely illegal plug-in unit can not be by registration, guarantees that application program can not call illegal plug-in unit.If the plug-in unit that the plugin manager judgement needs to register is legal plug-in unit, perform step S23, give the plug-in unit allocation space of new registration in the plug-in unit storage pool, calling interface is set namely for the plug-in unit of new registration in storage pool, called by the calling interface object.
Certainly, because plug-in unit can be constantly updated, the plug-in unit after renewal continues to continue to use original identification number and characteristic description, and calling interface object 30 still can find plug-in unit after renewal by identification number.Whether need to re-register as for the plug-in unit after upgrading, by the actual conditions of system development, determined.
All plug-in units due to the calling interface object in can system-oriented, but not all plug-in units all are stored in a plug-in unit storage pool, therefore there will be the calling interface that a certain plug-in unit is arranged 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, to application program, jumped to the memory address of this plug-in unit and carried out relevant instruction by application program.
As seen, by plug set, all plug-in units in 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, above-described embodiment is only the better embodiment of the present invention, during practical application, more change can also be arranged, for example, in non-open system,, because the user can not install new plug-in unit, can exempt the step of plug-in registration, be plugin manager as long as in the discovery system, corresponding plug-in unit is arranged, can call voluntarily this plug-in unit, no matter this plug-in unit whether register by process, such change also can realize purpose of the present invention.
It is emphasized that finally and the invention is not restricted to above-mentioned embodiment, as the variations such as change of the concrete steps of the change of plug set packing forms, plug-in registration, also should be included in the protection domain of the claims in the present invention.
Claims (5)
1. plug-in management method, comprise
Set up plugin manager in each application program;
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 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 to be called a certain plug-in unit, send call request to the plugin manager that described application program is corresponding, 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 to 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 in described plugin manager before finding after the required plug-in unit that calls and returning to memory address, if not registration is 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 whether Already in the required plug-in unit that calls in plug-in unit storage pool corresponding to described plugin manager, if do not have, after the required plug-in unit that calls of judgement is legal plug-in unit, give required plug-in unit memory allocated space of calling in described plug-in unit storage pool.
4. the plug-in management device, comprise
Be used for setting up in each application program the device of plugin manager;
It is characterized in that: also have
Be used for the device at the built-in vertical cutting spare storage pool of described plugin manager;
Give unique identification number be used for for each plug-in unit that is stored in described plug-in unit storage pool and encapsulate each described plug-in unit, the device of calling interface is provided correspondingly for each described plug-in unit;
Be used for the device that all plug-in units that all described plug-in unit storage pools are interior are packaged into plug set, the calling interface object of described plug set is provided to each described plugin manager;
Described application program is used for sending the device of call request to plugin manager corresponding to described application program when need to be called a certain plug-in unit;
Be used for the device that described plugin manager is searched the required plug-in unit that calls by the described plug set of described calling interface object reference, described plug set according to the identification number of the required plug-in unit that calls and returned to the memory address of the required plug-in unit that calls.
5. plug-in management device according to claim 4 is characterized in that:
Also comprise for before finding in described plugin manager after the required plug-in unit that calls and returning to memory address, judge whether the required plug-in unit that calls is registered in described plugin manager, if registration, do not register the device of operation to the required plug-in unit that calls.
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 CN102253840A (en) | 2011-11-23 |
| CN102253840B true 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) |
Families Citing this family (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103309700B (en) * | 2012-03-16 | 2016-05-18 | 腾讯科技（深圳）有限公司 | A kind of plug-in management control method and device |
| CN103365674B (en) * | 2012-03-31 | 2018-05-11 | 腾讯科技（深圳）有限公司 | A kind of plug-in management method based on mobile terminal, device and system |
| 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 |
| CN103473073A (en) * | 2013-09-25 | 2013-12-25 | 张新杰 | Method and system for fast calling out command calling interface |
| WO2015058546A1 (en) | 2013-10-25 | 2015-04-30 | 优视科技有限公司 | Webpage preloading method and device |
| 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 |
| CN104168136B (en) * | 2014-08-08 | 2018-04-06 | 小米科技有限责任公司 | The Notification Method and device of connection between external equipment and router |
| CN104301916B (en) * | 2014-11-07 | 2018-01-02 | 东南大学 | Test optimization method, apparatus and system based on mobile intelligent terminal universal card |
| CN104932887B (en) * | 2015-06-12 | 2018-02-02 | 北京京东尚科信息技术有限公司 | The plug-in management method and plateform system of a kind of plateform system |
| CN105373396B (en) * | 2015-08-14 | 2018-01-05 | 腾讯科技（深圳）有限公司 | Update of plug-in loading method and device in plug-platform |
| 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 |
| CN108388453B (en) * | 2018-01-15 | 2020-08-11 | 珠海格力电器股份有限公司 | 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 |
| 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 |
| CN114466070A (en) * | 2022-01-20 | 2022-05-10 | 精伦电子股份有限公司 | Middleware system, service request processing method, electronic device, and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1553332A (en) * | 2003-06-02 | 2004-12-08 | 联想(北京)有限公司 | Facility centralizing management method based by plugging technology |
| 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 |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7856517B2 (en) * | 2007-05-25 | 2010-12-21 | Red Hat, Inc. | Data management interface with configurable plugins that determines whether to monitor for configuration data |
-
2011
- 2011-08-04 CN CN2011102224925A patent/CN102253840B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1553332A (en) * | 2003-06-02 | 2004-12-08 | 联想(北京)有限公司 | Facility centralizing management method based by plugging technology |
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102253840A (en) | 2011-11-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102253840B (en) | Plugin management method and plugin manager | |
| CA2768752C (en) | Terminal device of non-android platform for executing android applications, and computer readable recording medium for storing program of executing android applications on non-android platform | |
| US9176713B2 (en) | Method, apparatus and program storage device that provides a user mode device interface | |
| CN107181679A (en) | A kind of port binding implementation method and device | |
| US20180307498A1 (en) | Driver Loading Method and Server | |
| CN105657191A (en) | Application increment upgrading method and system based on Android system | |
| CN102323879A (en) | Complete network middleware operation support platform and integration method of heterogeneous middleware | |
| CN112073448B (en) | Service isolation method and device for dual-system terminal | |
| CN106569880A (en) | Method and system for dynamically sharing resources between Android applications | |
| CN112667305A (en) | Page display method and device | |
| CN103997502A (en) | Safety enhanced model designing method based on cloud computing data center | |
| CN111090823A (en) | Integration platform of page application and application access method, device and equipment | |
| CN113010265A (en) | Pod scheduling method, scheduler, memory plug-in and system | |
| US20240345829A1 (en) | Mobile service upgrade method and apparatus, and terminal | |
| CN103530165B (en) | A kind of java solution that is applied to Internet of Things industry | |
| CN103473113A (en) | Universal virtual-machine adopting method | |
| CN115086166A (en) | Computing system, container network configuration method, and storage medium | |
| CN105677481A (en) | Method and system for processing data and electronic equipment | |
| CN111324357B (en) | Method for accessing application program to wind control platform and related equipment | |
| CN103186386A (en) | Application loading method and system | |
| CN109783132B (en) | Method and device for realizing system singleization and distribution | |
| CN101754156A (en) | Office data management method, device and charging system | |
| CN108804236B (en) | AIDL file sharing method and system | |
| CN116382944A (en) | Transaction-level memory data sharing method and device | |
| CN108809715A (en) | A kind of method and device of deployment management platform |
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 |