CN106325921B - Associated plug-in release method and device - Google Patents
Associated plug-in release method and device Download PDFInfo
- Publication number
- CN106325921B CN106325921B CN201610676765.6A CN201610676765A CN106325921B CN 106325921 B CN106325921 B CN 106325921B CN 201610676765 A CN201610676765 A CN 201610676765A CN 106325921 B CN106325921 B CN 106325921B
- Authority
- CN
- China
- Prior art keywords
- plug
- sub
- composite
- plugin
- version
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a method and a device for releasing a related plug-in. The method comprises the following steps: downloading a first composite plug-in of an application program, wherein the first composite plug-in comprises a plurality of mutually associated sub plug-ins and attribute information thereof; analyzing the first composite plug-in to obtain attribute information of the plurality of sub plug-ins, wherein the attribute information comprises version information of each sub plug-in; verifying whether the version information of each sub-plug-in meets a matching condition to obtain a verification result, wherein the matching condition refers to that the versions of the sub-plug-ins are matched with each other; and discarding the sub-plug-ins which do not meet the matching condition in the verification result, and releasing the sub-plug-ins which meet the matching condition in the verification result. The technical scheme realizes the purpose that a plurality of related sub-plug-ins can be upgraded simultaneously, avoids the condition that the sub-plug-ins cannot be used due to the fact that versions are not matched, and brings convenience for a user to upgrade the plurality of sub-plug-ins.
Description
Technical Field
The invention relates to the technical field of internet, in particular to a method and a device for releasing a related plug-in.
Background
In the prior art, for a plurality of associated plug-ins, the following issuing method is generally adopted: for example, for two associated plug-ins A and B, each of 100 versions, plug-in B defines an interface B1 for plug-in A to use. Later, plug-in B released the new version 101 and deleted interface B1, which in this case would cause a system crash if plug-in A were to recall plug-in B's interface B1.
To solve the above problem, adaptation is usually done when plug-in a is version 100, so that at least a system crash will not occur when a failure to call interface B1 is found. However, this method cannot meet the product requirement because after the plug-in B deletes the interface B1, there must be an update scheme to replace the interface, and at this time, if the plug-in a is not upgraded, the replacement update scheme cannot be used.
Another solution to the above problem is: no deletion processing is done for interfaces in the old version. Still taking the above plug-in a and plug-in B as an example, after the plug-in B releases the version 101, the interface B1 is not deleted, but a new interface B2 is added, in this case, if the product requires that the plug-in a also use the new interface B2 immediately, the plug-in a and the plug-in B must be upgraded at the same time, otherwise, if only the plug-in a is upgraded without upgrading the plug-in B, the situation that the new interface B2 cannot be called may also be caused.
It can be seen that the goal of having multiple associated plug-ins upgraded simultaneously is not achieved at present, which makes the release of multiple associated plug-ins very limited.
Disclosure of Invention
In view of the above, the present invention has been made to provide a method and apparatus for releasing an associated plug-in that overcome or at least partially solve the above problems.
According to an aspect of the present invention, there is provided a method for releasing an associated plug-in, including:
downloading a first composite plug-in of an application program, wherein the first composite plug-in comprises a plurality of mutually associated sub plug-ins and attribute information thereof;
analyzing the first composite plug-in to obtain attribute information of the plurality of sub plug-ins, wherein the attribute information comprises version information of each sub plug-in;
verifying whether the version information of each sub-plug-in meets a matching condition to obtain a verification result, wherein the matching condition refers to that the versions of the sub-plug-ins are matched with each other;
and discarding the sub-plug-ins which do not meet the matching condition in the verification result, and releasing the sub-plug-ins which meet the matching condition in the verification result.
Optionally, the attribute information further includes at least one of the number of sub-plugins in the first composite plugin, an offset of each sub-plugin in the first composite plugin, and an occupied length of each sub-plugin in the first composite plugin.
Optionally, the verifying whether the version information of each sub-plug-in meets a matching condition includes:
determining the version of the built-in plug-in of the application program;
judging whether the version of the sub plug-in is lower than that of the built-in plug-in or not;
and when the version of the sub plug-in is lower than that of the built-in plug-in, determining that the version information of the sub plug-in does not meet the matching condition.
Optionally, the verifying whether the version information of each sub-plug-in meets a matching condition includes:
acquiring a second composite plug-in of the application program, wherein the second composite plug-in and the first composite plug-in have the same sub plug-in;
determining whether the version of the same sub-plugin in the first composite plugin is higher than the version of the same sub-plugin in the second composite plugin;
when the version of the same sub-plugin in the first composite plugin is higher than the version of the same sub-plugin in the second composite plugin, determining that the version information of the same sub-plugin meets the matching condition.
Optionally, the method further comprises:
discarding the second composite insert.
Optionally, the application has a downloaded non-built-in plug-in of a preset type; the verifying whether the version information of each sub-plug-in meets the matching condition includes:
when the first composite plug-in comprises a sub plug-in which is the same as the non-built-in plug-in, judging whether the version of the sub plug-in is lower than that of the non-built-in plug-in;
and when the version of the sub-plug-in is lower than the version of the non-built-in plug-in, determining that the version information of the sub-plug-in meets the matching condition.
Optionally, the preset type is a V5 object type.
Optionally, the releasing the child plug-in meeting the matching condition in the verification result includes:
reading the number of the sub-inserts in the first composite insert;
reading the offset and the occupied length of the current sub-plug-in according to the number and the sequence of each sub-plug-in the first composite plug-in, and reading the content of the current sub-plug-in according to the offset and the occupied length;
and releasing the current sub-plug-in, reading the offset and the occupied length of the next sub-plug-in of the current sub-plug-in, and releasing the next sub-plug-in according to the offset and the occupied length.
Optionally, before releasing the daughter card satisfying the matching condition in the verification result, the method further includes:
marking the sub-plug-ins meeting the matching conditions in the verification result;
and storing the first composite plug-in with the mark in a preset memory table.
Optionally, the releasing the child plug-in meeting the matching condition in the verification result includes:
when a release request for the daughter card meeting the matching condition is received, inquiring the offset and the occupied length of the daughter card from the preset memory table;
positioning and jumping to the position of the daughter card according to the offset;
and reading the sub-plug-in content of the occupied length from the position, and releasing the read sub-plug-in.
Optionally, the method further comprises:
checking the attribute information of each sub-plug-in to judge whether the attribute information of each sub-plug-in to be released is correct, wherein the checking comprises at least one of the following items:
checking whether the offset of each sub-plug-in the first composite plug-in exceeds the total size of the first composite plug-in;
and checking whether the occupied length of each sub-plug-in the first composite plug-in exceeds a preset length.
According to another aspect of the present invention, there is provided a release device for an associated card, comprising:
the download module is suitable for downloading a first composite plug-in of an application program, and the first composite plug-in comprises a plurality of mutually related sub plug-ins and attribute information thereof;
the analysis module is suitable for analyzing the first composite plug-in unit to obtain attribute information of the plurality of sub plug-in units, and the attribute information comprises version information of each sub plug-in unit;
the verification module is suitable for verifying whether the version information of each sub-plug-in meets a matching condition to obtain a verification result, wherein the matching condition refers to that the versions of the sub-plug-ins are matched with each other;
and the releasing module is suitable for discarding the sub-plug-ins which do not meet the matching condition in the verification result and releasing the sub-plug-ins which meet the matching condition in the verification result.
Optionally, the attribute information further includes at least one of the number of sub-plugins in the first composite plugin, an offset of each sub-plugin in the first composite plugin, and an occupied length of each sub-plugin in the first composite plugin.
Optionally, the verification module is further adapted to determine a version of a built-in plug-in of the application; judging whether the version of the sub plug-in is lower than that of the built-in plug-in or not; and when the version of the sub plug-in is lower than that of the built-in plug-in, determining that the version information of the sub plug-in does not meet the matching condition.
Optionally, the verification module is further adapted to obtain a second composite plug-in of the application, where the second composite plug-in and the first composite plug-in have the same child plug-in; determining whether the version of the same sub-plugin in the first composite plugin is higher than the version of the same sub-plugin in the second composite plugin; when the version of the same sub-plugin in the first composite plugin is higher than the version of the same sub-plugin in the second composite plugin, determining that the version information of the same sub-plugin meets the matching condition.
Optionally, the apparatus further comprises:
a discarding module adapted to discard the second composite interposer.
Optionally, the application has a downloaded non-built-in plug-in of a preset type; the verification module is further adapted to determine whether the version of the daughter card is lower than that of the non-built-in plug-in when the first composite plug-in includes a daughter card identical to the non-built-in plug-in; and when the version of the sub-plug-in is lower than the version of the non-built-in plug-in, determining that the version information of the sub-plug-in meets the matching condition.
Optionally, the preset type is a V5 object type.
Optionally, the release module is further adapted to read the number of daughter cards in the first composite card; reading the offset and the occupied length of the current sub-plug-in according to the number and the sequence of each sub-plug-in the first composite plug-in, and reading the content of the current sub-plug-in according to the offset and the occupied length; and releasing the current sub-plug-in, reading the offset and the occupied length of the next sub-plug-in of the current sub-plug-in, and releasing the next sub-plug-in according to the offset and the occupied length.
Optionally, the apparatus further comprises:
the marking module is suitable for marking the sub-plug-ins meeting the matching conditions in the verification result before releasing the sub-plug-ins meeting the matching conditions in the verification result;
and the storage module is suitable for storing the first composite plug-in with the mark in a preset memory table.
Optionally, the releasing module is further adapted to query, when a release request for a daughter card meeting the matching condition is received, an offset and an occupied length of the daughter card from the preset memory table; positioning and jumping to the position of the daughter card according to the offset; and reading the sub-plug-in content of the occupied length from the position, and releasing the read sub-plug-in.
Optionally, the apparatus further comprises:
the verification module is suitable for verifying the attribute information of each sub-plug-in to judge whether the attribute information of each sub-plug-in to be released is correct or not, and the verification comprises at least one of the following items:
checking whether the offset of each sub-plug-in the first composite plug-in exceeds the total size of the first composite plug-in;
and checking whether the occupied length of each sub-plug-in the first composite plug-in exceeds a preset length.
By adopting the technical scheme provided by the embodiment of the invention, the purpose of binding, downloading and loading a plurality of associated plug-ins is realized by downloading the composite plug-in comprising a plurality of related interconnected plug-ins and further releasing each sub plug-in the composite plug-in, and when each sub plug-in is released, the version of each sub plug-in is firstly verified, so that the sub plug-ins which do not meet the matching condition (namely are not matched with the versions of other sub plug-ins) are discarded, and the sub plug-ins which meet the matching condition are released, so that one or more sub plug-ins which meet the matching condition in the composite plug-in can be released simultaneously, thereby realizing the purpose of simultaneously upgrading the plurality of mutually associated sub plug-ins, avoiding the condition that the sub plug-ins cannot be used due to the unmatched versions, and bringing convenience for upgrading the plurality of sub plug-ins by a user.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
The above and other objects, advantages and features of the present invention will become more apparent to those skilled in the art from the following detailed description of specific embodiments thereof, taken in conjunction with the accompanying drawings.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a schematic flow chart diagram of a method for releasing an associated plug-in according to one embodiment of the present invention;
FIG. 2 is a schematic diagram of a file format of a composite plug-in issued by V5 in a release method of an associated plug-in according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of step S103 in a release method of an associated plug-in according to an embodiment of the present invention;
fig. 4 is a schematic flowchart of step S103 in a release method of an associated plug-in according to another embodiment of the present invention;
fig. 5 is a schematic flowchart of step S103 in a release method of an associated plug-in according to another embodiment of the present invention;
FIG. 6 is a schematic flow chart diagram of step S104 of a release method of an associated plug-in according to one embodiment of the present invention;
fig. 7 is a schematic flowchart of step S104 in a release method of an associated plug-in according to another embodiment of the present invention;
FIG. 8 is a schematic block diagram of a release mechanism associated with a card in accordance with one embodiment of the present invention;
fig. 9 is a schematic block diagram of a release mechanism associated with a card in accordance with another embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Fig. 1 is a schematic flow chart of a release method of an associated plug-in according to an embodiment of the present invention. As shown in fig. 1, the release method of the associated plug-in may generally include steps S101-S104:
step S101, downloading a first composite plug-in of an application program, wherein the first composite plug-in comprises a plurality of mutually related sub plug-ins and attribute information thereof.
Step S102, analyzing the first composite plug-in to obtain attribute information of a plurality of sub plug-ins, wherein the attribute information comprises version information of each sub plug-in.
And step S103, verifying whether the version information of each sub-plug-in meets a matching condition to obtain a verification result, wherein the matching condition refers to that the versions of the sub-plug-ins are matched with each other. For example, when a version of a certain sub-plug-in is lower than versions of other sub-plug-ins, it may be considered that the version information of the sub-plug-in does not satisfy the matching condition.
And step S104, discarding the sub-plug-ins which do not meet the matching conditions in the verification result, and releasing the sub-plug-ins which meet the matching conditions in the verification result.
In one embodiment, after step S101 is executed (i.e., the first composite plug-in is downloaded), it may be determined whether the file name of the first composite plug-in meets a preset naming condition through a regular expression, where the preset naming condition may be customized by a user. And when the file name of the first composite plug-in meets the preset naming condition, continuing to execute the step S102. This determination can be performed to avoid the situation where the user downloads the wrong composite plugin. In one embodiment, when the file name of the first composite plug-in is determined to meet the preset naming condition, a V5FileInfo (custom) object can be further constructed to indicate that a V5 (i.e. V5 object type) issuing plug-in is currently downloaded.
In the above embodiment, the attribute information includes, in addition to the version information of each sub-plug-in, at least one of the number of sub-plug-ins in the first composite plug-in, the offset of each sub-plug-in the first composite plug-in, and the occupied length of each sub-plug-in the first composite plug-in. The offset can be used for positioning the position of each sub-plugin in the first composite plugin, and the occupied length can be used for determining the end position of each sub-plugin in the first composite plugin, so that each sub-plugin can be accurately read from the first composite plugin according to the attribute information.
Fig. 2 is a schematic diagram of a file format of a compound plugin issued by V5 in a release method of an associated plugin according to an embodiment of the present invention, where, as shown in fig. 2, count represents the number of child plugins included in the compound plugin, Pluign n inforcerd represents the content of the child plugins, the meaning of Name/low/high/ver/md5 is the same as that of Name/low/high/ver/md5 in a single plugin in the prior art, and is not described herein again, Offset represents an Offset of the child plugin in the compound plugin, and L ength represents an occupied length of the child plugin in the compound plugin.
By adopting the technical scheme provided by the embodiment of the invention, the purpose of binding, downloading and loading a plurality of associated plug-ins is realized by downloading the composite plug-in comprising a plurality of related interconnected plug-ins and further releasing each sub plug-in the composite plug-in, and when each sub plug-in is released, the version of each sub plug-in is firstly verified, so that the sub plug-ins which do not meet the matching condition (namely are not matched with the versions of other sub plug-ins) are discarded, and the sub plug-ins which meet the matching condition are released, so that one or more sub plug-ins which meet the matching condition in the composite plug-in can be released simultaneously, thereby realizing the purpose of simultaneously upgrading the plurality of mutually associated sub plug-ins, avoiding the condition that the sub plug-ins cannot be used due to the unmatched versions, and bringing convenience for upgrading the plurality of sub plug-ins by a user.
In the above embodiment, when step S103 is executed, various manners may be adopted to verify whether the version information of each sub-plug-in meets the matching condition, and several manners of verifying the version information are described below.
In one embodiment, the application has a built-in plug-in, which is the most basic plug-in to satisfy the application, and is not allowed to be reduced. Therefore, as shown in FIG. 3, after step S102 is performed (i.e., the first composite plug-in is parsed to obtain the attribute information of the plurality of sub-plug-ins), it can be verified whether the version information of each sub-plug-in satisfies the matching condition according to the following steps S301-S304.
Step S301, determining the version of the built-in plug-in of the application program.
Step S302, judging whether the version of the sub plug-in is lower than that of the built-in plug-in. If the version of the sub plug-in is lower than that of the built-in plug-in, executing step S303; otherwise, step S304 is performed.
Step S303, determining that the version information of the sub-plug-in does not meet the matching condition.
Step S304, determining that the version information of the sub-plug-in meets the matching condition.
In this embodiment, if it is determined that the version information of the sub-plug-in does not satisfy the matching condition, the sub-plug-in is discarded.
In one embodiment, the application has a downloaded second composite plug-in, which may be a different composite plug-in from the first composite plug-in or a plurality of composite plug-ins different from the first composite plug-in, and is not limited herein. Therefore, as shown in fig. 4, after step S102 is performed (i.e., the first composite plug-in is parsed to obtain the attribute information of the plurality of sub-plug-ins), it can be verified whether the version information of each sub-plug-in satisfies the matching condition according to the following steps S401-S404.
Step S401, a second composite plug-in of the application program is obtained, and the same sub plug-ins exist in the second composite plug-in and the first composite plug-in.
Step S402, judging whether the version of the same sub-plug-in the first composite plug-in is higher than that in the second composite plug-in. If the version of the same sub-plug-in the first composite plug-in is higher than the version in the second composite plug-in, executing step S403; otherwise, step S404 is performed.
In step S403, it is determined that the version information of the same sub-plug-in satisfies the matching condition.
Step S404, determining that the version information of the same sub-plug-in does not meet the matching condition.
In this embodiment, if it is determined that the version information of the same child plug-in does not satisfy the matching condition, the second composite plug-in is discarded on the premise that other conditions are satisfied (for example, the version information of other child plug-ins in the first composite plug-in satisfies the matching condition).
For example, the first composite plugin includes plugin a and plugin B, the second composite plugin includes plugin a and plugin C, the plugin a and the plugin C have the same daughter plugin a, and how the version of the daughter plugin a in the first composite plugin is higher than the version of the daughter plugin a in the second composite plugin, it is determined that the version information of the daughter plugin a in the first composite plugin satisfies the matching condition, and the second composite plugin may be discarded at this time.
In one embodiment, the application has an un-built-in plug-in of a downloaded preset type, which may be the V5 object type. At this time, as shown in fig. 5, after step S102 is performed (i.e., the first composite plug-in is parsed to obtain the attribute information of the plurality of sub-plug-ins), it may be verified whether the version information of each sub-plug-in satisfies the matching condition according to the following steps S501 to S503.
Step S501, when the first composite plug-in includes a sub plug-in identical to the non-built-in plug-in, judging whether the version of the sub plug-in is lower than that of the non-built-in plug-in. If the version of the sub-plug-in is lower than that of the non-built-in plug-in, executing step S502; otherwise, step S503 is executed.
Step S502, determining that the version information of the sub-plug-in meets the matching condition.
Step S503, determining that the version information of the sub plug-in does not satisfy the matching condition.
Taking the preset type as the V5 object type as an example, assuming that the first composite plug-in of the application includes sub plug-ins a and B, and the application further has plug-in a delivered by V5, where the plug-in a is not a built-in plug-in, if the version of the sub plug-in a in the first composite plug-in is lower than the version of the plug-in a delivered by V5, it is determined that the version information of the sub plug-in a in the first composite plug-in satisfies the matching condition, and at this time, the plug-in a delivered by V5 may be discarded. In this embodiment, the reason for keeping the daughter card a with the lower version is that the V5 issue card and the composite card are not configured for the same card at the same time in general, and if the V5 issue card and the composite card are configured at the same time, it is likely that the card belongs to the V5 issue card before, and then the composite card is configured for the card, so if the V5 issue card is allowed to continue to take effect, the principle and intention of configuring the composite card later will be damaged, the composite card cannot be issued, or the versions of the cards are mismatched, and therefore the V5 issue card is selected to be discarded in this case.
The way of verifying the version information of the daughter card provided in the above embodiments may be used alone, or may be used in combination with at least two of them. For example, if the three verification methods are combined, it can be determined that the version information of the child plug-in satisfies the matching condition only when the version of the verification child plug-in is higher than the version of the built-in plug-in, higher than the versions of the same child plug-ins in other composite plug-ins, and lower than the version of the same child plug-in issued by V5.
After the verification result is obtained, the daughter card meeting the matching condition can be released. The method for releasing the daughter card meeting the matching condition can be divided into two modes, one mode is to directly release the daughter card after verification is finished, and the other mode is to store the verification result after verification is finished and perform targeted release when the daughter card needs to be released subsequently. How to release the daughter card is described below separately for these two ways.
In one embodiment, after step S103 is performed, the daughter card satisfying the matching condition is released directly. Therefore, as shown in fig. 6, the daughter card satisfying the matching condition can be released as follows in steps S601 to S603.
Step S601, reading the number of the sub-inserts in the first composite insert. Typically, the first four bytes of the composite card are used to indicate the number of daughter cards in the composite card, and thus the number of daughter cards can be obtained by reading the first four bytes of the first composite card.
Step S602, reading the offset and the occupied length of the current daughter card according to the number and the sequence of each daughter card in the first composite card, and reading the content of the current daughter card according to the offset and the occupied length.
Step S603, releasing the current daughter card, reading the offset and the occupied length of the next daughter card of the current daughter card, and releasing the next daughter card according to the offset and the occupied length.
After the bytes used for indicating the number of the sub-plug-ins in the first composite plug-in, the attribute information and the content of the first sub-plug-in can be read. Specifically, the offset and the occupied length of the first daughter card are read, the offset and the occupied length of the first daughter card are used for positioning the starting position and the ending position of the first daughter card in the first composite card respectively, the content of the first daughter card can be accurately read according to the starting position and the ending position, and then the first daughter card is released. After the first sub-plug-in is read, the reading pointer stays at the next byte at the end of the content of the first sub-plug-in, so that the offset and the occupied length of the second sub-plug-in can be directly read, then the starting position and the ending position of the second sub-plug-in the first composite plug-in are positioned according to the offset and the occupied length of the second sub-plug-in, the content of the second sub-plug-in can be accurately read according to the starting position and the ending position, and the second sub-plug-in is released. And sequentially reading each daughter card according to the sequence of each daughter card in the first composite card until the Nth daughter card is read and released, wherein N is the number of the daughter cards in the first composite card. Whether the reading of the daughter cards in the first composite card is finished or not can be known through the number of the daughter cards in the first composite card read in advance.
In this embodiment, after the version information of each daughter card in the first composite card is verified, the daughter card satisfying the matching information is directly released, so that the time for first loading can be greatly saved, and the disadvantage is that more storage space of the terminal needs to be occupied. Therefore, if the memory space in the terminal is to be saved, the next release method can be adopted.
In one embodiment, after step S103 is executed, the method further includes the following steps: and marking the sub-plug-ins meeting the matching conditions in the verification result, and storing the first composite plug-ins with the marks in a preset memory table. Based on this, the daughter card satisfying the matching condition may be released as shown in steps S701 to S703 of fig. 7.
Step S701, when a release request for a daughter card satisfying the matching condition is received, querying an offset and an occupied length of the daughter card from a preset memory table.
And step S702, positioning and jumping to the position of the daughter card according to the offset. In this step, the offset can locate the start position of the daughter card in the first composite card, and therefore, the start position of the daughter card in the first composite card can be accurately located and jumped to according to the offset.
And step S703, reading the content of the sub-plug-in occupying the length from the jumped position, and releasing the read sub-plug-in. In the step, the end position of the daughter card can be accurately positioned according to the starting position and the occupied length of the daughter card. Therefore, as long as the offset and the occupied length of the daughter card in the first composite card are obtained, the daughter card can be accurately read and released, and all the daughter cards meeting the matching condition in the first composite card do not need to be released in sequence.
In this embodiment, the first composite plugin with the mark is stored in the preset memory table, so that when a user needs to release a certain plugin, the plugin can be accurately released by querying the plugin from the preset memory table, and all plugins meeting the matching condition in the first composite plugin do not need to be sequentially released, thereby saving a large amount of storage space in the terminal.
In any of the embodiments, after the first composite plug-in is analyzed to obtain the attribute information of the plurality of sub-plug-ins, the attribute information of each sub-plug-in needs to be checked to determine whether the attribute information of each sub-plug-in to be released is correct. Wherein, the checking of the attribute information of each sub-plug-in may include at least one of: and checking whether the offset of each sub-plug-in the first composite plug-in exceeds the total size of the first composite plug-in and checking whether the occupied length of each sub-plug-in the first composite plug-in exceeds a preset length. Specifically, when the offset of the daughter card in the first composite card is checked, if the offset of the daughter card in the first composite card exceeds the total size of the first composite card, it is determined that the offset of the card is wrong; when the occupation length of the daughter card in the first composite card is checked, if the occupation length of the daughter card in the first composite card exceeds a preset length, it is determined that the occupation length of the daughter card is wrong, and in general, the preset length may be set to be the total length of the first composite card. In this embodiment, whether the attribute information of each daughter card is correct is checked, so that attack on the first composite plugin by other external factors can be prevented, if the attribute information of each daughter card is wrong, it is indicated that the first composite plugin is attacked, and a user can take corresponding measures to the attack, so that release of the attacked daughter card is avoided. In addition, the verification of the offset and the occupied length of the daughter card is described only in an enumeration form, but does not represent that other attribute information is not verified, and in practical application, any attribute of the daughter card can be verified to prevent the composite card from being attacked, which is not enumerated herein.
FIG. 8 is a schematic block diagram of a release mechanism associated with a card in accordance with one embodiment of the present invention. As shown in fig. 8, the release means of the associated insert may generally comprise:
the downloading module 810 is adapted to download a first composite plug-in of the application program, wherein the first composite plug-in comprises a plurality of mutually associated sub plug-ins and attribute information thereof;
the analysis module 820 is coupled with the download module 810 and is suitable for analyzing the first composite plug-in to obtain attribute information of a plurality of sub plug-ins, wherein the attribute information comprises version information of each sub plug-in;
the verification module 830 is coupled with the analysis module 820 and is adapted to verify whether the version information of each daughter card meets a matching condition to obtain a verification result, wherein the matching condition refers to that the versions of each daughter card are matched with each other;
and the releasing module 840 is coupled with the verifying module 830 and is adapted to discard the daughter card which does not satisfy the matching condition in the verification result and release the daughter card which satisfies the matching condition in the verification result.
In one embodiment, the attribute information further includes at least one of a number of sub-plugins in the first composite plugin, an offset of each sub-plugin in the first composite plugin, and an occupied length of each sub-plugin in the first composite plugin.
In one embodiment, the verification module 830 is further adapted to determine a version of a built-in plug-in for the application; judging whether the version of the sub plug-in is lower than that of the built-in plug-in or not; and when the version of the sub-plug-in is lower than that of the built-in plug-in, determining that the version information of the sub-plug-in does not meet the matching condition.
In one embodiment, the verification module 830 is further adapted to obtain a second composite plug-in for the application, where the second composite plug-in has the same child plug-in as the first composite plug-in; judging whether the version of the same sub-plug-in the first composite plug-in is higher than that of the same sub-plug-in the second composite plug-in; and when the version of the same sub-plug-in the first composite plug-in is higher than that in the second composite plug-in, determining that the version information of the same sub-plug-in meets the matching condition.
In one embodiment, the apparatus further comprises a discard module adapted to discard the second composite insert.
In one embodiment, the application has a downloaded non-built-in plug-in of a preset type; the verification module 83 is further adapted to determine whether the version of the daughter card is lower than that of the non-built-in card when the first composite card includes the daughter card identical to the non-built-in card; and when the version of the sub-plug-in is lower than that of the non-built-in plug-in, determining that the version information of the sub-plug-in meets the matching condition.
In one embodiment, the preset type is a V5 object type.
In one embodiment, the release module 840 is further adapted to read the number of daughter cards in the first composite card; reading the offset and the occupied length of the current sub-plug-in according to the number and the sequence of each sub-plug-in the first composite plug-in, and reading the content of the current sub-plug-in according to the offset and the occupied length; and releasing the current sub-plug-in, reading the offset and the occupied length of the next sub-plug-in of the current sub-plug-in, and releasing the next sub-plug-in according to the offset and the occupied length.
In one embodiment, as shown in fig. 9, the above apparatus further comprises:
a marking module 850, coupled to the verification module 830, adapted to mark the daughter card satisfying the matching condition in the verification result before releasing the daughter card satisfying the matching condition in the verification result;
a storage module 860, coupled to the marking module 850 and the releasing module 840, is adapted to store the first composite plug-in with the mark in a predetermined memory table.
Correspondingly, the releasing module 840 is further adapted to query the offset and the occupied length of the daughter card from the preset memory table when receiving a releasing request for the daughter card meeting the matching condition; positioning and jumping to the position of the daughter card according to the offset; reading the child plug-in content occupying the length from the position, and releasing the read child plug-in.
In one embodiment, the above apparatus further comprises:
the verification module is suitable for verifying the attribute information of each sub-plug-in to judge whether the attribute information of each sub-plug-in to be released is correct or not, and the verification comprises at least one of the following items:
checking whether the offset of each sub-plug-in the first composite plug-in exceeds the total size of the first composite plug-in;
and checking whether the occupied length of each sub-plug-in the first composite plug-in exceeds a preset length.
By adopting the device provided by the embodiment of the invention, the purpose of binding, downloading, installing and loading a plurality of associated plug-ins is realized by downloading the composite plug-in comprising a plurality of related interconnected plug-ins, and then releasing each sub plug-in the composite plug-in, and the version of each sub plug-in is verified firstly when each sub plug-in is released, so that the sub plug-ins which do not meet the matching condition (namely are not matched with the versions of other sub plug-ins) are discarded, and the sub plug-ins which meet the matching condition are released, so that one or more sub plug-ins which meet the matching condition in the composite plug-in can be released simultaneously, thereby realizing the purpose of simultaneously upgrading the plurality of mutually associated sub plug-ins, avoiding the condition that the sub plug-ins cannot be used due to the unmatched versions, and bringing convenience for upgrading the plurality of sub plug-ins by a user.
It should be understood by those skilled in the art that the release apparatus for associated plug-in fig. 8 and fig. 9 can be used to implement the release scheme for associated plug-in, and the detailed description thereof should be similar to the description of the method part, and in order to avoid the complexity, the detailed description thereof is omitted.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the claims, any of the claimed embodiments may be used in any combination.
The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It will be appreciated by those skilled in the art that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components of the release apparatus associated with a card in accordance with embodiments of the present invention. The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
Thus, it should be appreciated by those skilled in the art that while a number of exemplary embodiments of the invention have been illustrated and described in detail herein, many other variations or modifications consistent with the principles of the invention may be directly determined or derived from the disclosure of the present invention without departing from the spirit and scope of the invention. Accordingly, the scope of the invention should be understood and interpreted to cover all such other variations or modifications.
The embodiment of the invention provides A1. a release method of an associated plug-in, which comprises the following steps:
downloading a first composite plug-in of an application program, wherein the first composite plug-in comprises a plurality of mutually associated sub plug-ins and attribute information thereof;
analyzing the first composite plug-in to obtain attribute information of the plurality of sub plug-ins, wherein the attribute information comprises version information of each sub plug-in;
verifying whether the version information of each sub-plug-in meets a matching condition to obtain a verification result, wherein the matching condition refers to that the versions of the sub-plug-ins are matched with each other;
and discarding the sub-plug-ins which do not meet the matching condition in the verification result, and releasing the sub-plug-ins which meet the matching condition in the verification result.
A2. The method according to a1, wherein the attribute information further includes at least one of the number of sub-plugins in the first composite plugin, the offset of each sub-plugin in the first composite plugin, and the occupied length of each sub-plugin in the first composite plugin.
A3. The method of A1 or A2, wherein the verifying whether the version information of each sub-plug-in meets a matching condition comprises:
determining the version of the built-in plug-in of the application program;
judging whether the version of the sub plug-in is lower than that of the built-in plug-in or not;
and when the version of the sub plug-in is lower than that of the built-in plug-in, determining that the version information of the sub plug-in does not meet the matching condition.
A4. The method of any of A1-A3, wherein the verifying whether the version information of the respective sub-plug-ins satisfies a matching condition comprises:
acquiring a second composite plug-in of the application program, wherein the second composite plug-in and the first composite plug-in have the same sub plug-in;
determining whether the version of the same sub-plugin in the first composite plugin is higher than the version of the same sub-plugin in the second composite plugin;
when the version of the same sub-plugin in the first composite plugin is higher than the version of the same sub-plugin in the second composite plugin, determining that the version information of the same sub-plugin meets the matching condition.
A5. The method of a4, wherein the method further comprises:
discarding the second composite insert.
A6. The method of any of a1-a5, wherein the application has a downloaded non-built-in plug-in of a preset type; the verifying whether the version information of each sub-plug-in meets the matching condition includes:
when the first composite plug-in comprises a sub plug-in which is the same as the non-built-in plug-in, judging whether the version of the sub plug-in is lower than that of the non-built-in plug-in;
and when the version of the sub-plug-in is lower than the version of the non-built-in plug-in, determining that the version information of the sub-plug-in meets the matching condition.
A7. The method of A6, wherein the preset type is a V5 object type.
A8. The method according to a2, wherein the releasing the child plug-in meeting the matching condition in the verification result includes:
reading the number of the sub-inserts in the first composite insert;
reading the offset and the occupied length of the current sub-plug-in according to the number and the sequence of each sub-plug-in the first composite plug-in, and reading the content of the current sub-plug-in according to the offset and the occupied length;
and releasing the current sub-plug-in, reading the offset and the occupied length of the next sub-plug-in of the current sub-plug-in, and releasing the next sub-plug-in according to the offset and the occupied length.
A9. The method according to A2, wherein before releasing the child plug-in satisfying the matching condition in the verification result, the method further comprises:
marking the sub-plug-ins meeting the matching conditions in the verification result;
and storing the first composite plug-in with the mark in a preset memory table.
A10. The method according to a9, wherein the releasing the child plug-in meeting the matching condition in the verification result includes:
when a release request for the daughter card meeting the matching condition is received, inquiring the offset and the occupied length of the daughter card from the preset memory table;
positioning and jumping to the position of the daughter card according to the offset;
and reading the sub-plug-in content of the occupied length from the position, and releasing the read sub-plug-in.
A11. The method of any one of a1-a10, wherein the method further comprises:
checking the attribute information of each sub-plug-in to judge whether the attribute information of each sub-plug-in to be released is correct, wherein the checking comprises at least one of the following items:
checking whether the offset of each sub-plug-in the first composite plug-in exceeds the total size of the first composite plug-in;
and checking whether the occupied length of each sub-plug-in the first composite plug-in exceeds a preset length.
The embodiment of the invention also provides a B12. a release device of the associated plug-in, which comprises:
the download module is suitable for downloading a first composite plug-in of an application program, and the first composite plug-in comprises a plurality of mutually related sub plug-ins and attribute information thereof;
the analysis module is suitable for analyzing the first composite plug-in unit to obtain attribute information of the plurality of sub plug-in units, and the attribute information comprises version information of each sub plug-in unit;
the verification module is suitable for verifying whether the version information of each sub-plug-in meets a matching condition to obtain a verification result, wherein the matching condition refers to that the versions of the sub-plug-ins are matched with each other;
and the releasing module is suitable for discarding the sub-plug-ins which do not meet the matching condition in the verification result and releasing the sub-plug-ins which meet the matching condition in the verification result.
B13. The apparatus of B12, wherein the attribute information further includes at least one of a number of sub-plugins in the first composite plugin, an offset of each sub-plugin in the first composite plugin, and an occupied length of each sub-plugin in the first composite plugin.
B14. The apparatus of B12 or B13, wherein the verification module is further adapted to determine a version of a built-in plug-in of the application; judging whether the version of the sub plug-in is lower than that of the built-in plug-in or not; and when the version of the sub plug-in is lower than that of the built-in plug-in, determining that the version information of the sub plug-in does not meet the matching condition.
B15. The apparatus of any of B12-B14, wherein the verification module is further adapted to obtain a second composite plug-in for the application, the second composite plug-in having a same child plug-in as the first composite plug-in; determining whether the version of the same sub-plugin in the first composite plugin is higher than the version of the same sub-plugin in the second composite plugin; when the version of the same sub-plugin in the first composite plugin is higher than the version of the same sub-plugin in the second composite plugin, determining that the version information of the same sub-plugin meets the matching condition.
B16. The apparatus of B15, wherein the apparatus further comprises:
a discarding module adapted to discard the second composite interposer.
B17. The apparatus according to any of B12-B16, wherein the application has a downloaded non-built-in plug-in of a preset type; the verification module is further adapted to determine whether the version of the daughter card is lower than that of the non-built-in plug-in when the first composite plug-in includes a daughter card identical to the non-built-in plug-in; and when the version of the sub-plug-in is lower than the version of the non-built-in plug-in, determining that the version information of the sub-plug-in meets the matching condition.
B18. The apparatus of B17, wherein the preset type is a V5 object type.
B19. The apparatus of B13, wherein the release module is further adapted to read the number of daughter cards in the first composite card; reading the offset and the occupied length of the current sub-plug-in according to the number and the sequence of each sub-plug-in the first composite plug-in, and reading the content of the current sub-plug-in according to the offset and the occupied length; and releasing the current sub-plug-in, reading the offset and the occupied length of the next sub-plug-in of the current sub-plug-in, and releasing the next sub-plug-in according to the offset and the occupied length.
B20. The apparatus of B13, wherein the apparatus further comprises:
the marking module is suitable for marking the sub-plug-ins meeting the matching conditions in the verification result before releasing the sub-plug-ins meeting the matching conditions in the verification result;
and the storage module is suitable for storing the first composite plug-in with the mark in a preset memory table.
B21. The apparatus according to B20, wherein the releasing module is further adapted to, when receiving a release request for a daughter card that satisfies the matching condition, query an offset and an occupied length of the daughter card from the preset memory table; positioning and jumping to the position of the daughter card according to the offset; and reading the sub-plug-in content of the occupied length from the position, and releasing the read sub-plug-in.
B22. The apparatus of any one of B12-B21, wherein the apparatus further comprises:
the verification module is suitable for verifying the attribute information of each sub-plug-in to judge whether the attribute information of each sub-plug-in to be released is correct or not, and the verification comprises at least one of the following items:
checking whether the offset of each sub-plug-in the first composite plug-in exceeds the total size of the first composite plug-in;
and checking whether the occupied length of each sub-plug-in the first composite plug-in exceeds a preset length.
Claims (16)
1. A release method of an associated plug-in includes:
downloading a first composite plug-in of an application program, wherein the first composite plug-in comprises a plurality of mutually associated sub plug-ins and attribute information thereof;
analyzing the first composite plug-in to obtain attribute information of the plurality of sub plug-ins, wherein the attribute information comprises version information of each sub plug-in;
verifying whether the version information of each sub-plug-in meets a matching condition to obtain a verification result, wherein the matching condition refers to that the versions of the sub-plug-ins are matched with each other;
discarding the sub-plug-ins which do not meet the matching condition in the verification result, and releasing the sub-plug-ins which meet the matching condition in the verification result;
the attribute information further includes at least one of the number of sub-plugins in the first composite plugin, the offset of each sub-plugin in the first composite plugin, and the occupied length of each sub-plugin in the first composite plugin;
wherein the method further comprises: checking the attribute information of each sub-plug-in to judge whether the attribute information of each sub-plug-in to be released is correct, wherein the checking comprises at least one of the following items: checking whether the offset of each sub-plug-in the first composite plug-in exceeds the total size of the first composite plug-in; checking whether the occupied length of each sub-plug-in the first composite plug-in exceeds a preset length or not;
the application program is provided with a downloaded non-built-in plug-in of a preset type; the verifying whether the version information of each sub-plug-in meets the matching condition includes:
when the first composite plug-in comprises a sub plug-in which is the same as the non-built-in plug-in, judging whether the version of the sub plug-in is lower than that of the non-built-in plug-in;
and when the version of the sub-plug-in is lower than the version of the non-built-in plug-in, determining that the version information of the sub-plug-in meets the matching condition.
2. The method of claim 1, wherein the verifying whether the version information of each sub-plug-in meets a matching condition comprises:
determining the version of the built-in plug-in of the application program;
judging whether the version of the sub plug-in is lower than that of the built-in plug-in or not;
and when the version of the sub plug-in is lower than that of the built-in plug-in, determining that the version information of the sub plug-in does not meet the matching condition.
3. The method of claim 1, wherein the verifying whether the version information of each sub-plug-in meets a matching condition comprises:
acquiring a second composite plug-in of the application program, wherein the second composite plug-in and the first composite plug-in have the same sub plug-in;
determining whether the version of the same sub-plugin in the first composite plugin is higher than the version of the same sub-plugin in the second composite plugin;
when the version of the same sub-plugin in the first composite plugin is higher than the version of the same sub-plugin in the second composite plugin, determining that the version information of the same sub-plugin meets the matching condition.
4. The method of claim 3, wherein the method further comprises:
discarding the second composite insert.
5. The method of claim 1, wherein the preset type is a V5 object type.
6. The method according to claim 1, wherein the releasing the child plug-in satisfying the matching condition in the verification result comprises:
reading the number of the sub-inserts in the first composite insert;
reading the offset and the occupied length of the current sub-plug-in according to the number and the sequence of each sub-plug-in the first composite plug-in, and reading the content of the current sub-plug-in according to the offset and the occupied length;
and releasing the current sub-plug-in, reading the offset and the occupied length of the next sub-plug-in of the current sub-plug-in, and releasing the next sub-plug-in according to the offset and the occupied length.
7. The method of claim 1, wherein before releasing the daughter card satisfying the matching condition in the verification result, the method further comprises:
marking the sub-plug-ins meeting the matching conditions in the verification result;
and storing the first composite plug-in with the mark in a preset memory table.
8. The method of claim 7, wherein the releasing the child plug-in the verification result that satisfies the matching condition comprises:
when a release request for the daughter card meeting the matching condition is received, inquiring the offset and the occupied length of the daughter card from the preset memory table;
positioning and jumping to the position of the daughter card according to the offset;
and reading the sub-plug-in content of the occupied length from the position, and releasing the read sub-plug-in.
9. A release device associated with a plug-in, comprising:
the download module is suitable for downloading a first composite plug-in of an application program, and the first composite plug-in comprises a plurality of mutually related sub plug-ins and attribute information thereof;
the analysis module is suitable for analyzing the first composite plug-in unit to obtain attribute information of the plurality of sub plug-in units, and the attribute information comprises version information of each sub plug-in unit;
the verification module is suitable for verifying whether the version information of each sub-plug-in meets a matching condition to obtain a verification result, wherein the matching condition refers to that the versions of the sub-plug-ins are matched with each other;
the releasing module is suitable for discarding the daughter card which does not meet the matching condition in the verification result and releasing the daughter card which meets the matching condition in the verification result;
the attribute information further includes at least one of the number of sub-plugins in the first composite plugin, the offset of each sub-plugin in the first composite plugin, and the occupied length of each sub-plugin in the first composite plugin;
wherein the apparatus further comprises:
the verification module is suitable for verifying the attribute information of each sub-plug-in to judge whether the attribute information of each sub-plug-in to be released is correct or not, and the verification comprises at least one of the following items:
checking whether the offset of each sub-plug-in the first composite plug-in exceeds the total size of the first composite plug-in;
checking whether the occupied length of each sub-plug-in the first composite plug-in exceeds a preset length or not;
the application program is provided with a downloaded non-built-in plug-in of a preset type; the verification module is further adapted to determine whether the version of the daughter card is lower than that of the non-built-in plug-in when the first composite plug-in includes a daughter card identical to the non-built-in plug-in; and when the version of the sub-plug-in is lower than the version of the non-built-in plug-in, determining that the version information of the sub-plug-in meets the matching condition.
10. The apparatus of claim 9, wherein the verification module is further adapted to determine a version of a built-in plug-in for the application; judging whether the version of the sub plug-in is lower than that of the built-in plug-in or not; and when the version of the sub plug-in is lower than that of the built-in plug-in, determining that the version information of the sub plug-in does not meet the matching condition.
11. The apparatus of claim 9, wherein the verification module is further adapted to obtain a second composite plug-in for the application, the second composite plug-in having a same child plug-in as the first composite plug-in; determining whether the version of the same sub-plugin in the first composite plugin is higher than the version of the same sub-plugin in the second composite plugin; when the version of the same sub-plugin in the first composite plugin is higher than the version of the same sub-plugin in the second composite plugin, determining that the version information of the same sub-plugin meets the matching condition.
12. The apparatus of claim 11, wherein the apparatus further comprises:
a discarding module adapted to discard the second composite interposer.
13. The apparatus of claim 9, wherein the preset type is a V5 object type.
14. The apparatus of claim 9, wherein the release module is further adapted to read the number of daughter cards in the first composite card; reading the offset and the occupied length of the current sub-plug-in according to the number and the sequence of each sub-plug-in the first composite plug-in, and reading the content of the current sub-plug-in according to the offset and the occupied length; and releasing the current sub-plug-in, reading the offset and the occupied length of the next sub-plug-in of the current sub-plug-in, and releasing the next sub-plug-in according to the offset and the occupied length.
15. The apparatus of claim 9, wherein the apparatus further comprises:
the marking module is suitable for marking the sub-plug-ins meeting the matching conditions in the verification result before releasing the sub-plug-ins meeting the matching conditions in the verification result;
and the storage module is suitable for storing the first composite plug-in with the mark in a preset memory table.
16. The apparatus according to claim 15, wherein the releasing module is further adapted to, when a release request for a daughter card satisfying the matching condition is received, query an offset and an occupied length of the daughter card from the preset memory table; positioning and jumping to the position of the daughter card according to the offset; and reading the sub-plug-in content of the occupied length from the position, and releasing the read sub-plug-in.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610676765.6A CN106325921B (en) | 2016-08-16 | 2016-08-16 | Associated plug-in release method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610676765.6A CN106325921B (en) | 2016-08-16 | 2016-08-16 | Associated plug-in release method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106325921A CN106325921A (en) | 2017-01-11 |
| CN106325921B true CN106325921B (en) | 2020-07-10 |
Family
ID=57740921
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610676765.6A Active CN106325921B (en) | 2016-08-16 | 2016-08-16 | Associated plug-in release method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106325921B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114398058A (en) * | 2017-09-27 | 2022-04-26 | 英特尔公司 | Firmware component with self-describing compliance information |
| CN114138376B (en) * | 2022-01-25 | 2022-06-24 | 统信软件技术有限公司 | Method for loading plug-in application, computing equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101030144A (en) * | 2006-02-28 | 2007-09-05 | 国际商业机器公司 | Software packaging method and system |
| CN101464805A (en) * | 2008-12-24 | 2009-06-24 | 中兴通讯股份有限公司 | Plug-in management method and system thereof |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104881311B (en) * | 2015-05-28 | 2018-06-08 | 南京南瑞继保电气有限公司 | The judgment method and device of a kind of edition compatibility |
-
2016
- 2016-08-16 CN CN201610676765.6A patent/CN106325921B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101030144A (en) * | 2006-02-28 | 2007-09-05 | 国际商业机器公司 | Software packaging method and system |
| CN101464805A (en) * | 2008-12-24 | 2009-06-24 | 中兴通讯股份有限公司 | Plug-in management method and system thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106325921A (en) | 2017-01-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10203951B2 (en) | Method and terminal for OTA updating | |
| CN104699511B (en) | Plug-in unit upgrade method and device | |
| CN106030546B (en) | The method of computer program | |
| CN108027741A (en) | Document handling method, device, terminal and storage medium based on patch upgrading | |
| CN110618903A (en) | Electronic equipment testing method and device | |
| WO2016183951A1 (en) | System upgrade method and terminal | |
| CN106843842B (en) | Method and device for updating application program configuration file | |
| US20180211044A1 (en) | Method and apparatus for upgrading embedded memory and terminal associated therewith | |
| CN106325921B (en) | Associated plug-in release method and device | |
| CN110716727A (en) | Software upgrading method and system | |
| US7434112B2 (en) | System and method for verifying validity of assembled PCI devices of a computer | |
| CN113553010B (en) | Optical disc file verification method, optical disc recording method and computing device | |
| CN109271315B (en) | Script code detection method, script code detection device, computer equipment and storage medium | |
| CN110275861A (en) | Date storage method and device, storage medium, electronic device | |
| CN109086065A (en) | A kind of method for upgrading software, system and terminal device | |
| US9600207B2 (en) | Integrated circuit with a patching function | |
| CN105988943B (en) | A kind of method and device driving wireless adapter | |
| CN108922607A (en) | Server, the method for data processing and storage medium | |
| CN105700917A (en) | Method and apparatus for synchronizing DLL and database | |
| WO2017071646A1 (en) | Method and apparatus for delivering device partition information | |
| US10496153B2 (en) | Method and system for binding chassis and components | |
| US20200004522A1 (en) | Selective download of a portion of a firmware bundle | |
| CN113407932B (en) | Channel identifier reporting method, system and storage medium | |
| CN109582334A (en) | The upgrade method and device of programmable logic device | |
| CN109359093A (en) | A kind of rule file update method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20211208 Address after: 300450 No. 9-3-401, No. 39, Gaoxin 6th Road, Binhai Science Park, high tech Zone, Binhai New Area, Tianjin Patentee after: 3600 Technology Group Co.,Ltd. Address before: 100088 room 112, block D, 28 new street, new street, Xicheng District, Beijing (Desheng Park) Patentee before: BEIJING QIHOO TECHNOLOGY Co.,Ltd. Patentee before: Qizhi software (Beijing) Co.,Ltd. |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20230711 Address after: 1765, floor 17, floor 15, building 3, No. 10 Jiuxianqiao Road, Chaoyang District, Beijing 100015 Patentee after: Beijing Hongxiang Technical Service Co.,Ltd. Address before: 300450 No. 9-3-401, No. 39, Gaoxin 6th Road, Binhai Science Park, high tech Zone, Binhai New Area, Tianjin Patentee before: 3600 Technology Group Co.,Ltd. |