CN117668006A - Page release method and device - Google Patents

Page release method and device Download PDF

Info

Publication number
CN117668006A
CN117668006A CN202211013946.2A CN202211013946A CN117668006A CN 117668006 A CN117668006 A CN 117668006A CN 202211013946 A CN202211013946 A CN 202211013946A CN 117668006 A CN117668006 A CN 117668006A
Authority
CN
China
Prior art keywords
page
data
content layer
version number
storing
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211013946.2A
Other languages
Chinese (zh)
Inventor
刘鹏辉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Jingdong Tuoxian Technology Co Ltd
Original Assignee
Beijing Jingdong Tuoxian Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Jingdong Tuoxian Technology Co Ltd filed Critical Beijing Jingdong Tuoxian Technology Co Ltd
Priority to CN202211013946.2A priority Critical patent/CN117668006A/en
Publication of CN117668006A publication Critical patent/CN117668006A/en
Pending legal-status Critical Current

Links

Abstract

The invention discloses a method and a device for publishing pages, and relates to the technical field of computers. One embodiment of the method comprises the following steps: responding to a page release request, acquiring configuration data of the page, wherein the configuration data comprises page style data, data to be released of at least one content layer contained in the page and relationship data between the page and the content layer; storing content layer data according to the data to be distributed of each content layer; under the condition that the content layer data of each content layer are successfully stored, storing page data according to the page style data and the relationship data between the page and the content layer; and under the condition that the page data is successfully stored, generating a query interface to finish the release of the page. According to the embodiment, the page release is completed, the content layer is taken as a release object, fine-granularity page release is performed, and the flexibility and release efficiency of the page release are improved.

Description

Page release method and device
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and apparatus for publishing a page.
Background
With the development and popularization of network technology, the network page is used as a carrier of data information and is integrated with various details of daily work and life, and plays an active important role in media popularization and other economic and educational aspects, and the success or failure of the release of the page is directly related to the display of the network page on a terminal as the most important step after the completion of the page construction. The current page publishing process is generally as follows: after the page is built, clicking a release button to store page configuration data in a database, providing a query interface by a server for a client to call, and finally displaying the queried configuration data on the page to realize specific functions of the page.
In the process of implementing the present invention, the inventor finds that the following problems exist in the prior art:
the existing page release is generally performed by taking the whole page as a unit, when the content of a certain part in the page needs to be modified, the page needs to be integrally released after the modification is finished, and fine granularity division of the page is lacked, so that the page release flexibility is low, and the page release efficiency is affected.
Disclosure of Invention
In view of this, the embodiments of the present invention provide a method and an apparatus for publishing a page, which respond to a page publishing request, obtain configuration data of the page, store content layer data according to the configuration data, store page data according to the configuration data in case of successful storage of the content layer data, and generate a query interface after successful storage of the page data, so that not only is the page published completed, but also fine-grained page publishing is performed with the content layer as a publishing object, thereby improving flexibility and publishing efficiency of the page publishing.
To achieve the above object, according to one aspect of the embodiment of the present invention, there is provided a method for publishing a page, including:
responding to a page release request, acquiring configuration data of the page, wherein the configuration data comprises page style data, data to be released of at least one content layer contained in the page and relationship data between the page and the content layer;
storing content layer data according to the data to be distributed of each content layer;
under the condition that the content layer data of each content layer are successfully stored, storing page data according to the page style data and the relationship data between the page and the content layer;
and under the condition that the page data is successfully stored, generating a query interface to finish the release of the page.
Optionally, storing content layer data according to the data to be distributed of each content layer includes: generating a content layer version number of each content layer; and carrying out associated storage on the content layer version number of each content layer and the data to be distributed so as to store the content layer data.
Optionally, storing the content layer version number of each content layer and the data to be distributed in an associated manner so as to store the content layer data, including: the content layer version number of each content layer and the data to be distributed are stored in a database in an associated mode; and storing the content layer identification, the content layer version number and the data to be distributed of each content layer in a cache in an associated manner.
Optionally, storing the content layer identifier, the content layer version number and the data to be distributed of each content layer in a cache in an associated manner, including: storing the content layer identification, the content layer version number and the data to be distributed of each content layer in the cache in a hash format in an associated manner; and storing the content layer identification and the content layer version number of each content layer in a list format in a cache in an associated manner.
Optionally, storing the page data according to the page style data and the relationship data between the page and the content layer, including: generating a page version number of the page; and carrying out association storage on the page version number, the page style data and the relationship data of the page and the content layer so as to store the page data.
Optionally, storing the page version number, the page style data, and the relationship data of the page and the content layer in association for storing page data includes: the page version number, the page style data and the relationship data of the page and the content layer are stored in a database in a related manner; and storing the page identification of the page, the page version number, the page style data and the relationship data of the page and the content layer in a cache in an associated manner.
Optionally, storing the page identifier of the page, the page version number, the page style data, and the relationship data of the page and the content layer in a cache in an associated manner, including: the page identification, the page version number and the page style data of the page are stored in the cache in a hash format in an associated mode; the page identification of the page, the page version number and the content layer identification of the content layer included in the page are stored in the cache in a list format in an associated mode, and the content layer identification of the content layer included in the page is obtained according to the relationship data of the page and the content layer; the page identification of the page, the page version number and the content layer version number of the content layer included in the page are stored in the cache in a list format in a correlated mode; and storing the page identification of the page and the page version number in a list format in the cache in an associated mode.
Optionally, the method further comprises: responding to a page configuration data query request received through the query interface, and searching configuration data of the page from the cache; searching configuration data of the page from the database under the condition of searching failure from the cache; and returning preset default data to serve as configuration data of the page under the condition that searching fails in the database.
According to a second aspect of an embodiment of the present invention, there is provided a page publishing device including:
the configuration data acquisition module is used for responding to a page release request and acquiring configuration data of the page, wherein the configuration data comprises page style data, data to be released of at least one content layer included in the page and relationship data between the page and the content layer;
the content layer data storage module is used for storing content layer data according to the data to be distributed of each content layer;
the page data storage module is used for storing page data according to the page style data and the relationship data of the page and the content layer under the condition that the content layer data of each content layer are successfully stored;
and the query interface generation module is used for generating a query interface to finish the release of the page under the condition that the page data is successfully stored.
According to a third aspect of an embodiment of the present invention, there is provided an electronic device for page publishing, including:
one or more processors;
storage means for storing one or more programs,
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method provided by the first aspect of the embodiments of the present invention.
According to a fourth aspect of embodiments of the present invention, there is provided a computer readable medium having stored thereon a computer program which when executed by a processor implements the method provided by the first aspect of embodiments of the present invention.
One embodiment of the invention has the following advantages or benefits: acquiring configuration data of a page by responding to a page release request, wherein the configuration data comprises page style data, data to be released of at least one content layer contained in the page and relationship data between the page and the content layer; storing content layer data according to the data to be distributed of each content layer; under the condition that the content layer data of each content layer are successfully stored, storing page data according to the page style data and the relationship data between the page and the content layer; under the condition that the page data storage is successful, a query interface is generated to finish the page release, the technical scheme of responding to the page release request, acquiring the configuration data of the page, storing the content layer data according to the configuration data, storing the page data according to the configuration data under the condition that the content layer data storage is successful, and after the page data storage is successful, generating the query interface, not only finishing the page release, but also taking the content layer as a release object, carrying out fine-granularity page release, and improving the flexibility and release efficiency of the page release.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic diagram of the main flow of a page publishing method according to an embodiment of the invention;
FIG. 2 is a flow diagram of content layer data storage according to an embodiment of the present invention;
FIG. 3 is a flow chart of page data storage according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a page query flow according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of main modules of a page publishing device according to an embodiment of the invention;
FIG. 6 is an exemplary system architecture diagram in which embodiments of the present invention may be applied;
fig. 7 is a schematic diagram of a computer system suitable for use in implementing an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, in which various details of the embodiments of the present invention are included to facilitate understanding, and are to be considered merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
The existing page release method generally takes the whole page as a unit to release, when the content of a certain part in the page needs to be modified, the page needs to be integrally released after the modification is finished, and the fine granularity of the page is not divided, so that the page release flexibility is not high, the page release efficiency is affected, and the actual application cannot be well met.
In order to solve the problems in the prior art, the invention provides a page publishing method, which responds to a page publishing request, acquires configuration data of a page, stores content layer data according to the configuration data, stores page data according to the configuration data under the condition that the content layer data is successfully stored, generates a query interface after the page data is successfully stored, completes the page publishing, and performs fine-granularity page publishing by taking a content layer as a publishing object, thereby improving the flexibility and the publishing efficiency of the page publishing.
In the description of the embodiments of the present invention, the terms and their meanings are as follows:
uuid: universally Unique Identifier is a universal unique identification code, which is a standard for software construction, and aims to enable all elements in a distributed system to have unique identification information;
Redis: is a high-performance key-value database.
Fig. 1 is a schematic diagram of main flow of a page publishing method according to an embodiment of the present invention, and as shown in fig. 1, the page publishing method according to an embodiment of the present invention includes the following steps S101 to S104.
Step S101, responding to a page release request, and acquiring configuration data of the page, wherein the configuration data comprises page style data, data to be released of at least one content layer included in the page, and relationship data between the page and the content layer.
Specifically, at the beginning of building a page, fine granularity division of a function module level is performed on the page according to the minimum service function of the page based on the planning design of the page, so as to obtain a plurality of content layers, such as a second killing module, a special price module, a display module of a certain commodity and the like of an e-commerce page, a uuid tool is called to generate a corresponding 32-bit page identifier and a content layer identifier for the page and each content layer, after the page is built, data to be distributed of each content layer is obtained, in addition, related style data and embedded point information are included in the page except for the data to be distributed of each content layer (the data to be distributed of each content layer and the relation data between the page and the content layer) included in the page, the key data information forms configuration data of the page, and when a page release request is received, the configuration data of the page corresponding to the page identifier is obtained through the page identifier included in the request so as to determine a data object to be distributed.
And step S102, storing the content layer data according to the data to be distributed of each content layer.
Specifically, the page is generally composed of a plurality of content layers, each content layer is independent from the other, and for the release of the page, firstly, the data to be released of all the content layers included in the page needs to be obtained from the configuration data, so as to store the data of the content layers.
According to one embodiment of the present invention, storing content layer data according to data to be distributed of each content layer includes: generating a content layer version number of each content layer; and carrying out associated storage on the content layer version number of each content layer and the data to be distributed so as to store the content layer data.
Specifically, an incremental content layer version number is generated through an increment method in the Redis tool, for example, a key is fixedly transmitted, the version number can be any character string v_cont, the first call returns 0, the version number is v_cont.0, the second call returns 1, and the corresponding version number is v_cont.1; considering that the data to be distributed of the content layer and the version number of the content layer have corresponding association relation, when the content layer is stored, the version number of the content layer and the data to be distributed of each content layer need to be stored in association.
According to another embodiment of the present invention, storing the content layer version number of each content layer and the data to be distributed in association for storing the content layer data includes: the content layer version number of each content layer and the data to be distributed are stored in a database in an associated mode; and storing the content layer identification, the content layer version number and the data to be distributed of each content layer in a cache in an associated manner.
Specifically, in view of the needs of multi-user, multi-scenario, high concurrency and high traffic frequent access query pages in practical application, the client directly requests to query content layer data through a database, so that faults such as long query time and server downtime easily occur.
According to still another embodiment of the present invention, storing the content layer identification, the content layer version number, and the data to be distributed of each of the content layers in association with a cache includes: storing the content layer identification, the content layer version number and the data to be distributed of each content layer in the cache in a hash format in an associated manner; and storing the content layer identification and the content layer version number of each content layer in a list format in a cache in an associated manner.
Specifically, for cache storage of content layer data, a Hash format is used to store the content layer data in a dis database, and content layer identification naming is specifically used, a content layer version number is used as a key, and data to be distributed corresponding to the content layer version number is used as a value, for example { name: app_content_data_content layer identification, key: content layer version number, value: configuring data, establishing a content layer identifier, a content layer version number and an association relation between data to be distributed, and storing the association relation in a Redis database; using list format, using content layer mark as key and corresponding content layer version number as value, placing the newly generated version number at the top of list, for example { key: app_content_version_content layer identification, value: content layer version number, storing the content layer identification and content layer version number of each content layer to the Redis database.
Through the database storage and the cache storage of the content layer data, redundant backup of the data storage is provided, and the operation pressure of a server and the database brought by subsequent data query is effectively relieved.
FIG. 2 is a schematic flow chart of content layer data storage in an embodiment of the present invention, first judging whether a content layer identifier of a content layer to be stored is correct, updating a release identifier field of the content layer to a release state when the content layer identifier is correct and generating an incremental content layer version number through Redis, checking main parameters such as the release state of the content layer, the content layer version number, data to be released, and the like, and after the verification is successful, performing associated storage on the updated release state, the content layer version number, and the data to be released of the content layer in a database; similarly, each main parameter of the content layer is checked again, after the verification is successful, the data to be distributed of the content layer is stored in the cache through hash format association, the version number of the content layer is stored in the cache through list format association, and the storage of the data of the content layer is completed. The other flow of the content layer data storage can be regarded as a transaction operation, either all the execution is successful or all the execution fails, if any step in the execution flow fails, the transaction execution fails, the process rolls back to the last version number according to the version number of the content layer, the storage failure is returned, and the flow is ended.
And step 103, under the condition that the content layer data of each content layer is successfully stored, storing page data according to the page style data and the relationship data between the page and the content layer.
Specifically, each content layer forms a page, after each content layer data is successfully stored, the execution success state is returned, and after the execution success state of all content layer data of the page is obtained, the page data is stored according to the page style data in the configuration data of the page and the relationship data between the page and the content layers.
According to one embodiment of the present invention, storing page data according to the page style data and the relationship data between the page and the content layer includes: generating a page version number of the page; and carrying out association storage on the page version number, the page style data and the relationship data of the page and the content layer so as to store the page data.
Specifically, generating an incremental page version number by an increment method in the Redis tool, for example, fixedly transmitting a key, which can be any character string v_exp of the page version number, wherein the first call returns 0, the version number is v_exp.0, the second call returns 1, and the corresponding version number is v_exp.1; besides considering that the page style data and the page version number have corresponding association relations, the configuration data of the page also comprises relation data of the page and the content layer, and the page version number, the page style data and the relation data of the page and the content layer need to be associated and stored.
According to another embodiment of the present invention, storing the page version number, the page style data, and the relationship data of the page and the content layer in association for storing page data includes: the page version number, the page style data and the relationship data of the page and the content layer are stored in a database in a related manner; and storing the page identification of the page, the page version number, the page style data and the relationship data of the page and the content layer in a cache in an associated manner.
Specifically, in order to improve the query efficiency of the page data and avoid operating the database directly and frequently, the embodiment of the invention provides a page data storage method based on cache storage, so that after the correctness of the page parameter check data, the page version number, the page style data and the relationship data of the page and the content layer are associated and stored in the database, and after the correctness of the secondary page parameter check data, the page identifier, the page version number, the page style data and the relationship data of the page and the content layer are associated and stored in the cache.
According to still another embodiment of the present invention, storing the page identification of the page, the page version number, the page style data, and the relationship data of the page and the content layer in a cache includes: the page identification, the page version number and the page style data of the page are stored in the cache in a hash format in an associated mode; the page identification of the page, the page version number and the content layer identification of the content layer included in the page are stored in the cache in a list format in an associated mode, and the content layer identification of the content layer included in the page is obtained according to the relationship data of the page and the content layer; the page identification of the page, the page version number and the content layer version number of the content layer included in the page are stored in the cache in a list format in a correlated mode; and storing the page identification of the page and the page version number in a list format in the cache in an associated mode.
Specifically, for cache storage of page data, the page data is stored in a dis database by using a Hash format, specifically using page identification naming, taking a page version number as a key, and page style data corresponding to the page version number as a value, for example { name: app_page_data_page identity, key: page version number, value: style data, establishing the association relationship of page identification, page version number and page style data, and storing the association relationship in a Redis database; obtaining a content layer identifier of a content layer included in the page according to the relationship data of the page and the content layer, using the page identifier and the page version number to name through list format, and using the content layer identifier as a key, for example { name: app_page_content_data_page identification_page version number, key: content layer identification }, storing the page identification of the page, the page version number and the content layer identification of the content layer included in the page in a Redis database in an associated manner; accordingly, by list format, using page identifier and page version number as key, and using content layer version number corresponding to the content layer identifier as value, for example { key: app_page_content_version_page identification_page VERSION number, value: content layer version number, storing the page identification of the page, the page version number and the content layer version number of the content layer included in the page in a Redis database in an associated manner; and then using list format, using page mark as key and page version number as value, and placing the newly generated version number at the top of list, for example { key: app_page_virtual_page_id, value: page version number }, storing the page identification of the page and the page version number in the Redis database in an associated manner.
Through the database storage and the cache storage of the page data, redundant backup of the data storage is provided, and the operation pressure of a server and a database brought by subsequent data query is effectively relieved.
FIG. 3 is a schematic flow chart of page data storage according to an embodiment of the present invention, where the storage of page data needs to be performed after all content layer data included in a page is successfully stored, all content layer data included in the page is stored according to the method for storing content layer data, after all content layer data is successfully stored, a release identification field of the page is updated to a release state, an incremental page version number is generated through Redis, main parameters such as a page identifier, a release state of the page, a page version number, page style data, and relationship data between the page and the content layer are checked, and after the verification is successful, the updated release state, page version number, page style data, and relationship data between the page and the content layer are associated and stored in a database; similarly, after the verification is successful, page identification, page version number and page style data of the page are stored in a cache in a hash format association mode, the page identification, the page version number and content layer identification of a content layer included in the page and the content layer version number corresponding to the content layer identification are stored in the cache in a list format association mode, and then the page identification and the page version number of the page are stored in the cache in a list format association mode, so that the storage of the page data is completed. The other page data storage flow can be regarded as a transaction operation, either all execution succeeds or all execution fails, if any step in the execution flow fails, the transaction execution fails, the page is rolled back to the last version number according to the version number of the page, the storage failure is returned, and the flow is ended.
Through the storage of the page data based on the content layer, the page release is fine-grained to a specific service function module, the flexibility of the page release is greatly improved, and particularly after the page release is finished, only the modified content layer data is required to be stored for the requirement of modifying individual content layers, the release efficiency of the page is improved, and even if the requirement of deleting or adding a certain content layer is required, the data storage of the newly added or deleted content layer can be firstly carried out, and then the page data storage is carried out.
Step S104, under the condition that the page data is successfully stored, generating a query interface to finish the release of the page.
Specifically, under the condition that the page data is successfully stored, a configuration data query interface of the page is generated at the server side, the release of the page is completed, the client side is enabled to call when accessing the page, and the queried configuration data is displayed on the page, so that the specific function of accessing the page is realized.
According to one embodiment of the invention, the method further comprises: responding to a page configuration data query request received through the query interface, and searching configuration data of the page from the cache; searching configuration data of the page from the database under the condition of searching failure from the cache; and returning preset default data to serve as configuration data of the page under the condition that searching fails in the database.
Specifically, according to the method for storing the configuration data of the page, when a page configuration data query request is received, the configuration data of the page is obtained by caching the Redis database preferentially, when the query cache fails, the configuration data of the page is obtained by the database, and if the query database fails, default data of the unified configuration center is returned to serve as the configuration data of the page. The specific method for inquiring the configuration data comprises the following steps: acquiring page identifiers and page version numbers according to a query request of received page configuration data, further acquiring relevant page data information such as page style data, determining all content layer identifiers and corresponding content layer version numbers included in the page according to the relationship data of the page and the content layers, acquiring content layer data according to the content layer identifiers and the content layer version numbers, and acquiring the page configuration data returned by the query interface according to the page data and the content layer data. In addition, synchronous or asynchronous queries are supported in the concrete query process, and if asynchronous queries, a thread pool needs to be created to execute multi-threaded queries.
FIG. 4 is a schematic diagram of a page query flow in an embodiment of the present invention, firstly querying page data in a cache, if the cache data is queried successfully, obtaining page data, querying relationship data between the page and a content layer in the cache, and if the query is successful, returning a query result; otherwise, carrying out content layer data query according to the relationship data of the page and the content layer in the database, returning a query result if the query is successful, otherwise, returning preset default data; in addition, if the query fails when the page data is queried, the page data in the database is queried, if the query fails, the preset default data is returned, otherwise, the content layer data is queried according to the relationship data of the page and the content layer, if the query is successful, the query result is returned, and otherwise, the preset default data is returned.
According to the page configuration data storage method, when the page is queried, the problems of long query time, server downtime and the like caused by high-concurrency and high-flow frequent query of the page can be effectively solved by utilizing the cache mechanism, so that the operation pressure of a server and a database is relieved to a great extent, and the query efficiency and the experience of a user are improved.
Fig. 5 is a schematic diagram of main modules of a page publishing device according to an embodiment of the present invention. As shown in fig. 5, the page publishing device 500 mainly includes a configuration data acquisition module 501, a content layer data storage module 502, a page data storage module 503, and a query interface generation module 504.
A configuration data obtaining module 501, configured to obtain configuration data of a page in response to a page publishing request, where the configuration data includes page style data, data to be published of at least one content layer included in the page, and relationship data between the page and the content layer;
the content layer data storage module 502 is configured to store content layer data according to data to be distributed of each content layer;
a page data storage module 503, configured to store page data according to the page style data and the relationship data between the page and the content layer when the content layer data of each content layer is successfully stored;
And the query interface generating module 504 is configured to generate a query interface to complete the publishing of the page if the page data is successfully stored.
According to one embodiment of the invention, the content layer data storage module 502 may also be configured to: generating a content layer version number of each content layer; and carrying out associated storage on the content layer version number of each content layer and the data to be distributed so as to store the content layer data.
According to another embodiment of the present invention, the content layer data storage module 502 may also be configured to: the content layer version number of each content layer and the data to be distributed are stored in a database in an associated mode; and storing the content layer identification, the content layer version number and the data to be distributed of each content layer in a cache in an associated manner.
According to yet another embodiment of the present invention, the content layer data storage module 502 may also be configured to: storing the content layer identification, the content layer version number and the data to be distributed of each content layer in the cache in a hash format in an associated manner; and storing the content layer identification and the content layer version number of each content layer in a list format in a cache in an associated manner.
According to one embodiment of the invention, the page data storage module 503 may also be configured to: generating a page version number of the page; and carrying out association storage on the page version number, the page style data and the relationship data of the page and the content layer so as to store the page data.
According to another embodiment of the present invention, the page data storage module 503 may be further configured to: the page version number, the page style data and the relationship data of the page and the content layer are stored in a database in a related manner; and storing the page identification of the page, the page version number, the page style data and the relationship data of the page and the content layer in a cache in an associated manner.
According to yet another embodiment of the present invention, the page data storage module 503 may be further configured to: the page identification, the page version number and the page style data of the page are stored in the cache in a hash format in an associated mode; the page identification of the page, the page version number and the content layer identification of the content layer included in the page are stored in the cache in a list format in an associated mode, and the content layer identification of the content layer included in the page is obtained according to the relationship data of the page and the content layer; the page identification of the page, the page version number and the content layer version number of the content layer included in the page are stored in the cache in a list format in a correlated mode; and storing the page identification of the page and the page version number in a list format in the cache in an associated mode.
According to an embodiment of the present invention, the page publishing device 500 may further include a query module (not shown in the figure) for: responding to a page configuration data query request received through the query interface, and searching configuration data of the page from the cache; searching configuration data of the page from the database under the condition of searching failure from the cache; and returning preset default data to serve as configuration data of the page under the condition that searching fails in the database.
FIG. 6 is an exemplary system architecture diagram in which embodiments of the present invention may be applied.
As shown in fig. 6, the system architecture 600 may include terminal devices 601, 602, 603, a network 604, and a server 605. The network 604 is used as a medium to provide communication links between the terminal devices 601, 602, 603 and the server 605. The network 604 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
A user may interact with the server 605 via the network 604 using the terminal devices 601, 602, 603 to receive or send messages, etc. Various communication client applications, such as a page publishing application, etc. (by way of example only) may be installed on the terminal devices 601, 602, 603.
The terminal devices 601, 602, 603 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 605 may be a server providing various services, such as a background management server (by way of example only) that provides support for page publication by a user using the terminal devices 601, 602, 603. The background management server can respond to a page release request to acquire configuration data of the page, wherein the configuration data comprises page style data, data to be released of at least one content layer included in the page and relationship data between the page and the content layer; storing content layer data according to the data to be distributed of each content layer; under the condition that the content layer data of each content layer are successfully stored, storing page data according to the page style data and the relationship data between the page and the content layer; in the case that the page data storage is successful, a query interface is generated to complete the processing such as the publication of the page, and the processing result (such as the publication data, etc. -just as an example) is fed back to the terminal device.
It should be noted that, the method for publishing a page provided in the embodiment of the present invention is generally executed by the server 605, and accordingly, the page publishing device is generally disposed in the server 605.
It should be understood that the number of terminal devices, networks and servers in fig. 6 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 7, there is illustrated a schematic diagram of a computer system 700 suitable for use in implementing a terminal device or server in accordance with an embodiment of the present invention. The terminal device or server shown in fig. 7 is only an example, and should not impose any limitation on the functions and scope of use of the embodiments of the present invention.
As shown in fig. 7, the computer system 700 includes a Central Processing Unit (CPU) 701, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the system 700 are also stored. The CPU 701, ROM 702, and RAM 703 are connected to each other through a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
The following components are connected to the I/O interface 705: an input section 706 including a keyboard, a mouse, and the like; an output portion 707 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 708 including a hard disk or the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. The drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read therefrom is mounted into the storage section 708 as necessary.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 709, and/or installed from the removable medium 711. The above-described functions defined in the system of the present invention are performed when the computer program is executed by a Central Processing Unit (CPU) 701.
The computer readable medium shown in the present invention may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination thereof.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present invention may be implemented in software or in hardware. The described units may also be provided in a processor, for example, described as: a processor comprising: the system comprises a configuration data acquisition module, a content layer data storage module, a page data storage module and a query interface generation module.
The names of these modules do not in any way limit the module itself, and for example, the content layer data storage module may also be described as "a module for storing content layer data according to data to be distributed of each of the content layers".
In another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the embodiment; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to include: responding to a page release request, acquiring configuration data of the page, wherein the configuration data comprises page style data, data to be released of at least one content layer contained in the page and relationship data between the page and the content layer; storing content layer data according to the data to be distributed of each content layer; under the condition that the content layer data of each content layer are successfully stored, storing page data according to the page style data and the relationship data between the page and the content layer; and under the condition that the page data is successfully stored, generating a query interface to finish the release of the page.
According to the technical scheme provided by the embodiment of the invention, the method has the following advantages or beneficial effects: acquiring configuration data of a page by responding to a page release request, wherein the configuration data comprises page style data, data to be released of at least one content layer contained in the page and relationship data between the page and the content layer; storing content layer data according to the data to be distributed of each content layer; under the condition that the content layer data of each content layer are successfully stored, storing page data according to the page style data and the relationship data between the page and the content layer; under the condition that the page data storage is successful, a query interface is generated to finish the page release, the technical scheme of responding to the page release request, acquiring the configuration data of the page, storing the content layer data according to the configuration data, storing the page data according to the configuration data under the condition that the content layer data storage is successful, and after the page data storage is successful, generating the query interface, not only finishing the page release, but also taking the content layer as a release object, carrying out fine-granularity page release, and improving the flexibility and release efficiency of the page release.
The described embodiments do not limit the scope of the invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can occur depending upon design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.

Claims (11)

1. A method of page publishing, comprising:
responding to a page release request, acquiring configuration data of the page, wherein the configuration data comprises page style data, data to be released of at least one content layer contained in the page and relationship data between the page and the content layer;
storing content layer data according to the data to be distributed of each content layer;
under the condition that the content layer data of each content layer are successfully stored, storing page data according to the page style data and the relationship data between the page and the content layer;
and under the condition that the page data is successfully stored, generating a query interface to finish the release of the page.
2. The method of claim 1, wherein storing content layer data based on the data to be distributed for each of the content layers comprises:
Generating a content layer version number of each content layer;
and carrying out associated storage on the content layer version number of each content layer and the data to be distributed so as to store the content layer data.
3. The method of claim 2, wherein storing the content layer version number of each of the content layers in association with the data to be distributed for storage of content layer data comprises:
the content layer version number of each content layer and the data to be distributed are stored in a database in an associated mode;
and storing the content layer identification, the content layer version number and the data to be distributed of each content layer in a cache in an associated manner.
4. The method of claim 3, wherein storing the content layer identification, content layer version number, and data to be distributed association for each of the content layers in a cache comprises:
storing the content layer identification, the content layer version number and the data to be distributed of each content layer in the cache in a hash format in an associated manner;
and storing the content layer identification and the content layer version number of each content layer in a list format in a cache in an associated manner.
5. The method of claim 1, wherein storing page data based on the page style data and the relationship data of the page and the content layer comprises:
Generating a page version number of the page;
and carrying out association storage on the page version number, the page style data and the relationship data of the page and the content layer so as to store the page data.
6. The method of claim 5, wherein storing the page version number, the page style data, and the relationship data of the page and content layer in association for storage of page data comprises:
the page version number, the page style data and the relationship data of the page and the content layer are stored in a database in a related manner;
and storing the page identification of the page, the page version number, the page style data and the relationship data of the page and the content layer in a cache in an associated manner.
7. The method of claim 6, wherein storing the page identification of the page, the page version number, the page style data, and the relationship data association of the page with the content layer in a cache comprises:
the page identification, the page version number and the page style data of the page are stored in the cache in a hash format in an associated mode;
The page identification of the page, the page version number and the content layer identification of the content layer included in the page are stored in the cache in a list format in an associated mode, and the content layer identification of the content layer included in the page is obtained according to the relationship data of the page and the content layer;
the page identification of the page, the page version number and the content layer version number of the content layer included in the page are stored in the cache in a list format in a correlated mode;
and storing the page identification of the page and the page version number in a list format in the cache in an associated mode.
8. The method according to claim 3 or 6, characterized in that the method further comprises:
responding to a page configuration data query request received through the query interface, and searching configuration data of the page from the cache;
searching configuration data of the page from the database under the condition of searching failure from the cache;
and returning preset default data to serve as configuration data of the page under the condition that searching fails in the database.
9. A page issuing apparatus, characterized by comprising:
the configuration data acquisition module is used for responding to a page release request and acquiring configuration data of the page, wherein the configuration data comprises page style data, data to be released of at least one content layer included in the page and relationship data between the page and the content layer;
The content layer data storage module is used for storing content layer data according to the data to be distributed of each content layer;
the page data storage module is used for storing page data according to the page style data and the relationship data of the page and the content layer under the condition that the content layer data of each content layer are successfully stored;
and the query interface generation module is used for generating a query interface to finish the release of the page under the condition that the page data is successfully stored.
10. A mobile electronic device terminal, comprising:
one or more processors;
storage means for storing one or more programs,
when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-8.
11. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-8.
CN202211013946.2A 2022-08-23 2022-08-23 Page release method and device Pending CN117668006A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211013946.2A CN117668006A (en) 2022-08-23 2022-08-23 Page release method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211013946.2A CN117668006A (en) 2022-08-23 2022-08-23 Page release method and device

Publications (1)

Publication Number Publication Date
CN117668006A true CN117668006A (en) 2024-03-08

Family

ID=90071697

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211013946.2A Pending CN117668006A (en) 2022-08-23 2022-08-23 Page release method and device

Country Status (1)

Country Link
CN (1) CN117668006A (en)

Similar Documents

Publication Publication Date Title
CN110019350B (en) Data query method and device based on configuration information
US10257110B2 (en) Using a template to update a stack of resources
CN110262807B (en) Cluster creation progress log acquisition system, method and device
CN108846753B (en) Method and apparatus for processing data
CN112380227B (en) Data synchronization method, device, equipment and storage medium based on message queue
CN112764751A (en) Interface generation method and device, interface request method and device and storage medium
WO2021203918A1 (en) Method for processing model parameters, and apparatus
CN116303608A (en) Data processing method and device for application service
CN113900907B (en) Mapping construction method and system
CN111338834A (en) Data storage method and device
CN112948498A (en) Method and device for generating global identification of distributed system
WO2022156087A1 (en) Data blood relationship establishing method and apparatus, computer device, and storage medium
CN110674426B (en) Webpage behavior reporting method and device
CN113641706A (en) Data query method and device
CN112199923A (en) Identification generation method, system, device and medium based on distributed system
CN115545639B (en) Financial business processing method, device, electronic equipment and storage medium
CN114840562B (en) Distributed caching method and device for business data, electronic equipment and storage medium
CN111767495A (en) Method and system for synthesizing webpage
CN117668006A (en) Page release method and device
CN111796878B (en) Resource splitting and loading method and device applied to single-page application
CN113779122B (en) Method and device for exporting data
CN113076343A (en) Data query method, device, equipment and storage medium
CN112948733A (en) Interface maintenance method, device, computing equipment and medium
CN111324374A (en) Application program registration method and device based on application performance management system
CN113760860B (en) Data reading method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination