A method, apparatus, device, and medium for publishing content management architecture.

Abstract

This invention relates to the field of blockchain technology and provides a method for publishing content management architectures. The method includes the following steps: obtaining a newly developed content management architecture and an initial content management architecture; assigning unique identity information to the newly developed content management architecture to generate a corresponding target content management architecture; assigning unique identity information to the initial content management architecture to generate a corresponding intermediate content management architecture; performing normalization processing on the intermediate content management architecture to generate a corresponding target content management architecture; and publishing the target content management architecture generated from the newly developed content management architecture and the target content management architecture generated from the initial content management architecture. This invention's method for publishing content management architectures facilitates mutual referencing between architectures within different CMS systems.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of blockchain, in particular to a content management architecture publishing processing method and device, equipment and medium. BACKGROUND

[0002] A content management system (CMS) is a software system designed to publish network content to the Internet, between the front end of the network and the back end of the office system. The core part of the reusability in the existing CMS system is basically maintained independently through different standards. The maintenance standards of different CMS systems are different, which leads to the fact that the architectures in different CMS systems cannot be directly referenced to each other. The reference between the architectures in different CMS systems is cumbersome. SUMMARY

[0003] In view of the above-mentioned shortcomings of the prior art, the purpose of the present application is to provide a content management architecture publishing processing method, which can facilitate the mutual reference between the architectures in different CMS systems.

[0004] In a first aspect, a content management architecture publishing processing method is provided, which comprises the following steps:

[0005] obtaining a newly developed content management architecture and an initial content management architecture;

[0006] assigning a unique identity information to the newly developed content management architecture to generate a corresponding target content management architecture;

[0007] assigning a unique identity information to the initial content management architecture to generate a corresponding intermediate content management architecture;

[0008] performing a regularization processing on the intermediate content management architecture to generate a corresponding target content management architecture;

[0009] publishing the target content management architecture generated by the newly developed content management architecture and the target content management architecture generated by the initial content management architecture.

[0010] In a second aspect, a content management architecture publishing processing device is provided, which comprises:

[0011] a data acquisition module for acquiring a newly developed content management architecture and an initial content management architecture;

[0012] an identity assignment module for assigning a unique identity information to the newly developed content management architecture to generate a corresponding target content management architecture, and assigning a unique identity information to the initial content management architecture to generate a corresponding intermediate content management architecture;

[0013] The processing module is used to normalize the intermediate content management architecture and generate a corresponding target content management architecture; and

[0014] The publishing module is used to publish the target content management architecture generated by the newly developed content management architecture and the target content management architecture generated by the initial content management architecture.

[0015] Thirdly, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the processing method for publishing the content management architecture.

[0016] Fourthly, a computer-readable storage medium is provided, the computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the content management architecture publishing processing method.

[0017] As described above, the present invention provides a method for publishing a content management architecture. For the referencing process between modules within different CMS systems, a new target content management architecture is developed according to a preset standard. This transforms the initial content management architectures within different CMS systems into a unified standard target content management architecture, which is then published. This enables different CMS systems to reference different target content management architectures, unifying the target content management architectures of CMS systems and achieving reuse of the target content management architecture across different CMS systems. Attached Figure Description

[0018] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 The flowchart shown is a processing method for publishing a content management architecture according to the present invention.

[0020] Figure 2 Displayed as Figure 1 A partial flowchart of step S10.

[0021] Figure 3 Displayed as Figure 1 Another part of the flowchart for step S10.

[0022] Figure 4 Displayed as Figure 1 A flowchart of step S40.

[0023] Figure 5 is shown as Figure 1 Another flowchart of step S40.

[0024] Figure 6 is shown as Figure 1 A flowchart of step S50.

[0025] Figure 7 is shown as a schematic diagram of a content management architecture of different content management systems.

[0026] Figure 8 is shown as a schematic diagram of mutual reference between different content management systems.

[0027] Figure 9 is shown as a structural schematic diagram of a processing device of a content management architecture of the present application.

[0028] Figure 10 is shown as a structural schematic diagram of a computer device of the present application.

[0029] Figure 11 is shown as another structural schematic diagram of a computer device of the present application. DETAILED DESCRIPTION

[0030] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative labor fall within the scope of protection of the present application.

[0031] The processing method of the content management architecture release provided by the embodiments of the present application can be applied in a blockchain. There are multiple content management systems on the blockchain, and each content management system has a corresponding content management architecture. When different content management systems need to reference the corresponding content management architecture, a newly developed content management architecture and an initial content management architecture can be obtained first. Then, the newly developed content management architecture is given a unique identity information, a corresponding target content management architecture is generated, the initial content management architecture is given a unique identity information, and a corresponding intermediate content management architecture is generated. The intermediate content management architecture is then normalized to generate the target content management architecture. Finally, all target content management architectures are imported into the same release file, and the release file is deployed into the blockchain to release the target content management architecture, so that the content management system can reference the content management architecture in other content management systems. The present application will be described in detail through specific embodiments.

[0032] Please refer to Figure 1 as shown, Figure 1 A flowchart of a processing method for publishing a content management architecture provided by an embodiment of the present application is shown. The processing method can include the following steps:

[0033] Step S10, obtaining a newly developed content management architecture and an initial content management architecture;

[0034] Step S20, assigning a unique identity information to the newly developed content management architecture to generate a corresponding target content management architecture;

[0035] Step S30, assigning a unique identity information to the initial content management architecture to generate a corresponding intermediate content management architecture;

[0036] Step S40, performing normalization processing on the intermediate content management architecture to generate a corresponding target content management architecture;

[0037] Step S50, publishing the target content management architecture generated by the newly developed content management architecture and the target content management architecture generated by the initial content management architecture to a blockchain.

[0038] Please refer to Figure 2 As shown, in an embodiment of the present application, when step S10 is performed, a newly developed content management architecture is obtained. Specifically, step S10 can include the following steps:

[0039] Step S11, obtaining newly developed content;

[0040] Step S12, performing normalization processing on the newly developed content to generate a newly developed content management architecture;

[0041] Step S13, based on a preset standard life cycle function and a publish / subscribe design pattern, monitoring the newly developed content management architecture to enable message publishing when the newly developed content management architecture is in a design phase, a compilation phase and a running phase.

[0042] In an embodiment of the present application, when steps S11, S12 and S13 are executed, that is, the newly developed content is acquired, the newly developed content is normalized, the newly developed content management architecture is generated, and the newly developed content management architecture is monitored based on the preset standard life cycle function and the publish / subscribe design pattern, so that the newly developed content management architecture is in the design stage, the compilation stage and the running stage. In particular, the blockchain can be divided into public chain, private chain and alliance chain. The public chain is the abbreviation of public blockchain (Public Block Chain), the private chain is the abbreviation of private blockchain (Private Block Chain), and the alliance chain is the abbreviation of consortium blockchain (Consortium Block Chain, also known as industry blockchain). The three kinds of blockchains all adopt the basic blockchain architecture. The public chain can be a kind of blockchain deployment model in which any blockchain service client can use, any node can access, and all access nodes can participate in reading and writing data. The private chain can be a kind of blockchain deployment model in which only a single client can use, only authorized nodes can access, and access nodes can participate in reading and writing data according to rules. The alliance chain can be a kind of blockchain deployment model in which only a group of specific clients can use, only authorized nodes can access, and access nodes can participate in reading and writing data according to rules.

[0043] In an embodiment of the present application, when a new content management system (CMS) needs to be created on a public chain, a private chain and a consortium chain, a new development content corresponding to the new content management system to be developed can be obtained first, the new development content is normalized, and the new development content is uniformly developed according to a preset standard to generate a new development content management architecture, so that the generated new development content management architecture conforms to the specification on the blockchain, and the new development content management architecture can be referenced by other content management systems. On the blockchain, a standard life cycle function and a publish / subscribe design pattern can be preset to monitor the development process of the new development content management architecture in real time, so that the new development content management architecture is in the design stage, the compilation stage and the running stage. The standard life cycle function can monitor the creation period, the mounting period, the updating period, the unloading period and the exception stage of the new development content management architecture. The creation period can be the period from before the creation of the new development content management architecture (moduleBeforeCreate) to after the completion of the creation (moduleDidCreated). The mounting period can be the period from the initial creation of the component instance of the new development content management architecture (moduleBeforeMount) to after the completion of the creation (moduleDidMount). The updating period can be the period from before the re-rendering of the new development content management architecture (moduleBeforeUpdate) to after the completion of the rendering (moduleDidUpdate). The unloading period can be the period from before the destruction of the new development content management architecture (moduleBeforeDestroy) to after the destruction (moduleDidDestroy). The exception stage can be the period from the occurrence of an exception in the running of the new development content management architecture (errorCaptured) to the reporting of the exception (errorReport). The standard life cycle function on the blockchain can monitor each stage of the new development content management architecture, and at the same time, the publish / subscribe design pattern on the blockchain can realize event bus (eventBus) message communication, such as PubSub.js: git: / / github.com / mroderick / PubSubJS.git, and then the publish / subscribe design pattern can be used for message publishing.

[0044] In an embodiment of the present application, when step S20 is performed, a unique identity information is assigned to the newly developed content management architecture, and a corresponding target content management architecture is generated. The identity information corresponds to the source code of the newly developed content management architecture. Specifically, after the newly developed content management architecture is generated according to the newly developed content, the unique identity information can be assigned to the newly developed content management architecture by using the characteristics of the blockchain, and the corresponding target content management architecture is generated to correspond to the source code of the newly developed content management architecture, thereby ensuring the fine-grained version control of the CMS system on the target content management architecture. When the target content management architecture is referenced by other CMS systems at a later stage, the version information and the current state information of the target content management architecture can be obtained.

[0045] Referring to FIG. 1, Figure 3 In an embodiment of the present application, when step S10 is performed, the initial content management architecture is obtained. Specifically, step S10 can include the following steps:

[0046] Step S14, according to the preset release condition, polling all content management architectures in the blockchain, and determining whether the content management architecture meets the preset release condition;

[0047] Step S15, if the content management architecture meets the preset release condition, the content management architecture is saved as the initial content management architecture, and the next content management architecture is read until all content management architectures in the blockchain are inquired;

[0048] Step S16, if the content management architecture does not meet the preset release condition, the content management architecture is skipped, and the next content management architecture is read until all content management architectures in the blockchain are inquired.

[0049] In an embodiment of the present application, when steps S14, S15 and S16 are executed, that is, according to the preset publishing condition, all content management architectures in the blockchain are polled to determine whether the content management architectures meet the preset publishing condition. If the content management architectures meet the preset publishing condition, the content management architectures are saved as initial content management architectures, and the next content management architecture is read until all content management architectures in the blockchain are polled. If the content management architectures do not meet the preset publishing condition, the content management architectures are skipped, and the next content management architecture is read until all content management architectures in the blockchain are polled. Specifically, since there are multiple CMS systems on public chains, private chains and alliance chains, when a content management architecture in a CMS system or a type of CMS system needs to be referenced, all content management architecture resources in the blockchain are currently installed as dependencies. When designing, the required modules are selected from the dependencies for compilation and deployment. This can affect the core compilation system in the CMS system when the number of content management architectures reaches a certain level. Therefore, the blockchain can poll all content management architectures in the blockchain according to the externally preset publishing condition to determine whether the content management architectures meet the preset publishing condition, so as to query the content management architectures that meet the preset publishing condition and export them as corresponding initial content management architectures. The initial content management architectures can be customized and modified later so that the modified initial content management architectures can be referenced by other CMS systems.

[0050] In an embodiment of the present application, when step S40 is executed, the initial content management architecture is assigned a unique identity information to generate a corresponding intermediate content management architecture. The identity information corresponds to the source code of the initial content management architecture. Specifically, after the initial content management architecture is obtained according to the preset publishing condition, the unique identity information can be assigned to the initial content management architecture by using the characteristics of the blockchain to generate a corresponding intermediate content management architecture. The source code of the intermediate content management architecture is corresponded to, thereby ensuring the fine-grained version control of the CMS system on the intermediate content management architecture. When the intermediate content management architecture is referenced by other CMS systems later, the version information and the current state information of the current intermediate content management architecture can be obtained.

[0051] In one embodiment of the present invention, the target content management architecture and the intermediate content management architecture can be stored in a version control system repository to maintain the source code of the target content management architecture and the intermediate content management architecture. The version control system repository includes a distributed version control system repository (Git) and a centralized version control system repository (SVN). Specifically, after obtaining the target content management architecture and the intermediate content management architecture, the source code of the target content management architecture and the intermediate content management architecture can be stored in the distributed version control system repository (Git) and the centralized version control system repository (SVN) to maintain the source code of the target content management architecture and the intermediate content management architecture, enabling different storage methods.

[0052] In one embodiment of the present invention, a preset object notation configuration file can be used to map the storage addresses of the target content management architecture and the intermediate content management architecture. The preset object notation configuration file can be identified, and different version control system repository identifiers can be requested based on the type of different version control system repositories. Specifically, the blockchain can maintain an object notation (JavaScript Object Notation, JSON) configuration file to map the addresses of different target content management architectures and intermediate content management architectures. For example, a CMS system within the blockchain can identify the JSON configuration file and then request different version control system repository identifiers based on the type of different version control system repositories.

[0053] Please see Figure 4 As shown, in one embodiment of the present invention, when step S40 is executed, the intermediate content management architecture is normalized to generate the target content management architecture. Specifically, step S40 may include the following steps:

[0054] Step S41: Obtain the method name of the intermediate content management architecture;

[0055] Step S42: Initialize the method names of the intermediate content management architecture to generate the target content management architecture.

[0056] In one embodiment of the present invention, when steps S41 and S42 are executed, the method names of the intermediate content management architecture are obtained, and the method names of the intermediate content management architecture are initialized to generate the target content management architecture. Specifically, since there can be multiple CMS systems on the blockchain, there can also be multiple intermediate content management architectures. The formats of the intermediate content management architectures within different CMS systems are different and cannot be directly referenced; multiple intermediate content management architectures need to be converted into a unified and standardized content management architecture. Therefore, a pre-defined object simplification (JSON) file can be used on the blockchain to map the method names of the target content management architecture, and the method names of the intermediate content management architectures can be initialized to generate the target content management architecture. For example, the standard method name for blockchain content management architecture is `initial`, but the method name for intermediate content management architecture A is `firstInit`, and the method name for intermediate content management architecture B is `onInitial`. A JSON file can be used to map the method names of intermediate content management architecture A and intermediate content management architecture B, changing `firstInit` to `initial` and `onInitial` to `initial`. This ensures that the method names of intermediate content management architecture A and intermediate content management architecture B are identical to the standard method names for blockchain content management architecture, allowing them to be referenced by other CMS systems.

[0057] Please see Figure 5 As shown, in one embodiment of the present invention, when step S40 is executed, the intermediate content management architecture is normalized to generate the target content management architecture. Specifically, step S40 may include the following steps:

[0058] Step S43: Based on the preset code compilation file, convert the source code of the method names of the intermediate content management architecture into an abstract syntax tree;

[0059] Step S44: Traverse the abstract syntax tree and call the conversion plugin in the code compilation file to add, delete, and modify the abstract syntax tree;

[0060] Step S45: Convert the added, deleted, and modified abstract syntax tree into source code of method names, and compile the method names of the intermediate content management architecture to generate the target content management architecture.

[0061] In one embodiment of the present invention, when executing steps S43, S44, and S45, specifically, when it is necessary to transform multiple intermediate content management architectures into a unified and standardized content management architecture, a pre-defined code compilation file can be used to compile the method names of the intermediate content management architectures, transforming them into standard method names consistent with the blockchain's content management architecture. For example, the source code of intermediate content management architecture A can be transformed into a corresponding abstract syntax tree based on the code compilation file. Then, the abstract syntax tree can be traversed, and a transformation plugin can be called to add, delete, and modify the abstract syntax tree, converting the transformed abstract syntax tree back into source code and generating the target content management architecture. At this point, the method name of the target content management architecture A is changed from firstInit to initial.

[0062] Please see Figure 6 As shown, when step S50 is executed, the target content management architecture generated by the newly developed content management architecture and the target content management architecture generated by the initial content management architecture are published to the blockchain. Specifically, step S50 may include the following steps:

[0063] Step S51: Import the target content management architecture generated by the newly developed content management architecture and the target content management architecture generated by the initial content management architecture into the same release file, and change the status of the target content management architecture to the pending release status. The target content management architecture includes module name information, module version information, creator information, and module description information.

[0064] Step S52: Publish the release file to the blockchain to publish the target content management architecture and change the status of the target content management architecture to the published state.

[0065] In one embodiment of the present invention, when step S51 is executed, the target content management architecture generated by the newly developed content management architecture and the target content management architecture generated by the initial content management architecture are imported into the same release file, and the status of the target content management architecture is set to a pending release state. The target content management architecture includes module name information, module version information, creator information, and module description information. Specifically, after generating corresponding target content management architectures based on the newly developed content management architecture and corresponding target content management architectures based on the intermediate content management architecture, multiple target content management architectures can be obtained. To manage these multiple target content management architectures uniformly, they can be imported into the same release file. At this time, the target content management architecture is in a pending release state and cannot be referenced by other CMS systems. The target content management architecture may include module name information, module version information, creator information, and module description information. The module name information represents the name of the target content management architecture. The module version information represents the current version information of the target content management architecture, i.e., unique identity information. The creator information indicates who created it. The module description information is a description of the target content management architecture.

[0066] In one embodiment of the present invention, when step S52 is executed, the release file is published to the blockchain to release the target content management architecture, and the status of the target content management architecture is set to the published state. Specifically, when it is necessary to release the target content management architecture, the release file can be published to the blockchain so that other CMS systems can reference the target content management architecture in the release file. During the release, the status of the target content management architecture can be changed to the published state so that other CMS systems can successfully reference it.

[0067] Please see Figure 7 and Figure 8As shown, in one embodiment of the present invention, both the personal blog (WordPress, WP) system 100 and the medical CMS system 300 on the blockchain are CMS systems, but they cannot reference each other. For example, the WP core system 200 of the WP system 100 may include multiple plugins, such as WP plugin 1, WP plugin 2, WP plugin 3, etc. The core compilation system 400 of the medical CMS system 300 may include multiple modules, such as module 1, module 2, module 3, etc. The WP system 100 cannot directly reference the modules within the medical CMS system 300, and the medical CMS system 300 cannot directly reference the plugins within the WP system 100. Therefore, by setting a module reference layer 500 and a module compatibility layer 600 on the blockchain, the WP system 100 and the medical CMS system 300 can reference each other through the cooperation of the module reference layer 500 and the module compatibility layer 600.

[0068] As can be seen, in the above solution, for the referencing process between modules within different CMS systems on the blockchain, a new target content management architecture is developed according to a preset standard. By transforming the initial content management architecture within different CMS systems on the blockchain into a unified standard target content management architecture and publishing the target content management architecture within the blockchain, different CMS systems on the blockchain can reference different target content management architectures. This unifies the target content management architectures of CMS systems, realizes the reuse of target content management architectures between different CMS systems and the ecosystem, and reduces the development cost of CMS modules.

[0069] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0070] Please see Figure 9 As shown, the present invention also provides a processing device for publishing content management architecture, which corresponds one-to-one with the processing methods in the above embodiments. This processing device may include a data acquisition module 10, an identity assignment module 20, a processing module 30, and a publishing module 40. Detailed descriptions of each functional module are as follows:

[0071] In one embodiment of the present invention, the data acquisition module 10 can be used to acquire a newly developed content management architecture and an initial content management architecture. Specifically, the data acquisition module 10 can be used to acquire newly developed content, perform normalization processing on the newly developed content, generate a newly developed content management architecture, monitor the newly developed content management architecture based on preset standard lifecycle functions and publish-subscribe design patterns, so that the newly developed content management architecture publishes messages when it is in the design phase, compilation phase, and runtime phase, and poll all content management architectures in the blockchain according to preset publishing conditions to determine whether the content management architecture meets the preset publishing conditions. If the content management architecture meets the preset publishing conditions, it is saved as the initial content management architecture, and the next content management architecture is read, until all content management architectures in the blockchain have been queried. If the content management architecture does not meet the preset publishing conditions, it is skipped, and the next content management architecture is read, until all content management architectures in the blockchain have been queried.

[0072] In one embodiment of the present invention, the identity assignment module 20 can be used to assign unique identity information to a newly developed content management architecture to generate a corresponding target content management architecture, and to assign unique identity information to an initial content management architecture to generate a corresponding intermediate content management architecture. Specifically, the identity assignment module 20 can be used to assign unique identity information to a newly developed content management architecture to generate a corresponding target content management architecture, wherein the identity information corresponds to the source code of the newly developed content management architecture; to assign unique identity information to the initial content management architecture to generate a corresponding intermediate content management architecture, wherein the identity information corresponds to the source code of the initial content management architecture; and to store the target content management architecture and the intermediate content management architecture in a version control system repository for maintaining the source code of the target content management architecture and the intermediate content management architecture. The version control system repository includes a distributed version control system repository Git and a centralized version control system repository SVN. Based on a preset object shorthand configuration file, the storage addresses of the target content management architecture and the intermediate content management architecture are mapped, the preset object shorthand configuration file is identified, and different version control system repository identifiers are requested according to different version control system repository types.

[0073] In one embodiment of the present invention, the processing module 30 can be used to normalize the intermediate content management architecture and generate the target content management architecture. Specifically, the processing module 30 can be used to map the method names of the intermediate content management architecture based on a preset object spectrum file, initialize the method names of the intermediate content management architecture, and generate the target content management architecture. Alternatively, the processing module 30 can also be used to convert the source code of the method names of the intermediate content management architecture into an abstract syntax tree based on a preset code compilation file, traverse the abstract syntax tree, call the conversion plugin in the code compilation file to add, delete, and modify the abstract syntax tree, and convert the added, deleted, and modified abstract syntax tree into source code to generate the target content management architecture.

[0074] In one embodiment of the present invention, the publishing module 40 can be used to publish multiple target content management architectures to the blockchain. Specifically, the publishing module 40 can be used to import multiple target content management architectures into the same publishing file, change the status of the target content management architecture to a pending publishing state, wherein the target content management architecture includes module name information, module version information, creator information, and module description information, publish the publishing file to the blockchain to publish the target content management architecture, and change the status of the target content management architecture to a published state.

[0075] This invention provides a processing device for publishing a content management architecture. Addressing the referencing process between modules within different CMS systems on a blockchain, it develops a new target content management architecture according to a preset standard. By transforming the initial content management architectures within different CMS systems on the blockchain into a unified standard target content management architecture and publishing this target content management architecture within the blockchain, different CMS systems on the blockchain can reference different target content management architectures. This unifies the target content management architectures of CMS systems, achieving target content management architecture reuse between different CMS systems and the ecosystem, and reducing the development cost of CMS modules.

[0076] For specific limitations regarding the processing device, please refer to the limitations on the processing method above, which will not be repeated here. Each module in the aforementioned processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in hardware within or independently of the processor in the computer device, or stored in software in the memory of the computer device, so that the processor can call and execute the operations corresponding to each module.

[0077] Please see Figure 10As shown, the present invention also provides a computer device, which can be a server. The computer device includes a processor, memory, a network interface, and a database connected via a system bus. The processor of the computer device provides computing and control capabilities. The memory of the computer device includes non-volatile and / or volatile storage media and internal memory. The non-volatile storage media stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface of the computer device is used to communicate with external clients via a network connection. When the computer program is executed by the processor, it implements the functions or steps of a content management architecture publishing processing method.

[0078] Please see Figure 11 As shown, the present invention also provides another computer device, which can be a client. This computer device includes a processor, memory, network interface, display screen, and input device connected via a system bus. The processor of this computer device provides computing and control capabilities. The memory of this computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The network interface of this computer device is used to communicate with an external server via a network connection. When the computer program is executed by the processor, it implements the functions or steps of a content management architecture publishing processing method.

[0079] In one embodiment of the present invention, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it performs the following steps:

[0080] Obtain the newly developed content management architecture and the initial content management architecture;

[0081] Assign a unique identity to the newly developed content management architecture and generate the corresponding target content management architecture;

[0082] Assign a unique identity to the initial content management architecture to generate the corresponding intermediate content management architecture;

[0083] The intermediate content management architecture is standardized to generate the corresponding target content management architecture;

[0084] The target content management architecture generated by the newly developed content management architecture and the target content management architecture generated by the initial content management architecture are published into the blockchain.

[0085] In one embodiment of the present invention, a computer-readable storage medium is provided having a computer program stored thereon, wherein the computer program, when executed by a processor, performs the following steps:

[0086] Obtain the newly developed content management architecture and the initial content management architecture;

[0087] Assign a unique identity to the newly developed content management architecture and generate the corresponding target content management architecture;

[0088] Assign a unique identity to the initial content management architecture to generate the corresponding intermediate content management architecture;

[0089] The intermediate content management architecture is standardized to generate the corresponding target content management architecture;

[0090] The target content management architecture generated by the newly developed content management architecture and the target content management architecture generated by the initial content management architecture are published into the blockchain.

[0091] It should be noted that the functions or steps that can be implemented by the computer-readable storage medium or computer device described above can be referred to in the foregoing method embodiments. To avoid repetition, they will not be described one by one here.

[0092] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.

[0093] In the description of this specification, the references to terms such as "this embodiment," "example," "specific example," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0094] The embodiments of the present invention disclosed above are merely illustrative of the invention. The embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the content of this specification. This specification selects and specifically describes these embodiments to better explain the principles and practical applications of the invention, thereby enabling those skilled in the art to better understand and utilize the invention. The invention is limited only by the claims and their full scope and equivalents.

Claims

1. A method for processing content management architecture publishing, characterized in that, The application is applied to a blockchain, a module reference layer and a module compatibility layer are arranged on the blockchain, content management systems refer to each other through cooperation of the module reference layer and the module compatibility layer, and the processing method comprises the following steps: An initial content management architecture is obtained; A newly developed content is obtained and normalized, and the newly developed content is uniformly developed according to a preset standard to generate a newly developed content management architecture; A standard life cycle function and a publish / subscribe design pattern are used to monitor the newly developed content management architecture to enable the newly developed content management architecture to publish messages in a design stage, a compilation stage and a running stage; The newly developed content management architecture is given unique identity information to generate a corresponding target content management architecture; The initial content management architecture is given unique identity information to generate a corresponding intermediate content management architecture; The intermediate content management architecture is normalized to generate a corresponding target content management architecture; The target content management architecture generated by the newly developed content management architecture and the target content management architecture generated by the initial content management architecture are imported into a same publish file, and a state of the target content management architecture is changed to a to-be-published state; The publish file is published, and the state of the target content management architecture is changed to a published state.

2. The method of claim 1, wherein the content management architecture publication is a web page. The step of obtaining the initial content management architecture comprises the following steps: All content management architectures are polled according to a preset publish condition to determine whether the content management architectures meet the publish condition; If the publish condition is met, the content management architecture is saved as an initial content management architecture, and a next content management architecture is read until all content management architectures are polled; and If the publish condition is not met, the content management architecture is skipped, and a next content management architecture is read until all content management architectures are polled.

3. The method of claim 1, wherein the content management architecture publication is a web page. The step of normalizing the intermediate content management architecture to generate a corresponding target content management architecture comprises the following steps: A method name of the intermediate content management architecture is obtained; The method name of the intermediate content management architecture is initialized to generate a target content management architecture.

4. The method of claim 1, wherein the content management architecture publication is a web page. The step of normalizing the intermediate content management architecture to generate a corresponding target content management architecture comprises the following steps: Based on a preset code compilation file, source code of the method name of the intermediate content management architecture is converted into an abstract syntax tree; The abstract syntax tree is traversed, and a transformation plug-in in the code compilation file is called to add, delete or modify the abstract syntax tree; The abstract syntax tree after addition, deletion or modification is converted into source code of the method name, and the method name of the intermediate content management architecture is compiled to generate the target content management architecture.

5. A processing apparatus for content management architecture publication, characterized by, The processing method for publishing the content management architecture is applied to any one of claims 1 to 4, and the processing device comprises: A data acquisition module is configured to obtain a newly developed content management architecture and an initial content management architecture; an identity assigning module, configured to assign a unique identity information to the newly developed content management architecture to generate a corresponding target content management architecture, assign a unique identity information to the initial content management architecture to generate a corresponding intermediate content management architecture; a processing module, configured to perform a regularization processing on the intermediate content management architecture to generate a corresponding target content management architecture; and a publishing module, configured to publish the target content management architecture generated by the newly developed content management architecture and the target content management architecture generated by the initial content management architecture.

6. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, The processor executes the computer program to implement the steps of the processing method for publishing the content management architecture according to any one of claims 1 to 4.

7. A computer-readable storage medium storing a computer program, wherein the computer program comprises the following steps of: receiving a request for a resource from a client; determining whether the client is authorized to access the resource; and if the client is authorized to access the resource, providing the resource to the client. The computer program is executed by the processor to implement the steps of the processing method for publishing the content management architecture according to any one of claims 1 to 4.

Images