CN117909007A - Page dynamic delivery method and device, computer equipment and storage medium - Google Patents

Abstract

The embodiment of the invention discloses a page dynamic delivery method, a page dynamic delivery device, computer equipment and a storage medium. The method comprises the following steps: acquiring a registration request; marking a put-in area in a page according to the registration request; generating a delivery content DSL with layout information in a rasterization layout dragging mode; analyzing the put content DSL to construct a rendering product for rendering the specified dom element; configuring a release strategy and establishing release association relationship data; rendering the release content according to the release strategy and the release association relation data. By implementing the method of the embodiment of the invention, the support of self-defined release content, self-defined release strategy and real-time change of release content can be realized, and invasive modification of a service system is not required.

Description

Page dynamic delivery method and device, computer equipment and storage medium

Technical Field

The present invention relates to a method for delivering pages, and more particularly, to a method, an apparatus, a computer device, and a storage medium for dynamically delivering pages.

Background

Dynamic delivery is an implementation of an internet technology capability that presents different content to different users in a page, which technology is commonly used in operational scenarios such as active page content delivery or advertisement content delivery. Generally, the dynamic delivery of a page is to meet the requirements of self-defining delivery content, self-defining delivery strategy, real-time change of delivery content and presentation of different content by different people.

Chinese patent CN2022113293043 discloses a method and system for dynamic delivery of operator positions. The dynamic delivery method comprises the following steps: the method comprises the steps of intercepting an entry method in a service code of a service request response in a front-end system, inquiring bound operation content according to configuration in a back-end system, injecting the operation content into a service request context, analyzing the operation content in the service context in the front-end system, and rendering an operation bit according to an analysis result, wherein the operation content dynamic delivery is embodied as the movement of a canner picture in an operation position and the movement of a jump link. The above patent realizes the differentiated display of the released content in a dynamic data mode, the releasing mode is limited by the page layout of the operation position, the dynamic releasing aim can be realized only by configuring dynamic data under the fixed template, the page layout of the operation position can not be dynamically changed, the template can not be customized to meet the requirement of complex scenes, the released content can only be configured through background data, and the releasing effect can not be seen when the released content is configured in an intuitive mode. The method has invasiveness to the service system, and the dynamic rendered data logic needs to be invaded into the actual service system, so that the development cost and the system coupling degree are increased, and the method has no universality.

Therefore, it is necessary to design a new method to support custom delivery content, custom delivery policy, and real-time change of delivery content, and no invasive modification is required to the service system.

Disclosure of Invention

The invention aims to overcome the defects of the prior art and provides a page dynamic delivery method, a device, computer equipment and a storage medium.

In order to achieve the above purpose, the present invention adopts the following technical scheme: the page dynamic delivery method comprises the following steps:

Acquiring a registration request;

marking a put-in area in a page according to the registration request;

Generating a delivery content DSL with layout information in a rasterization layout dragging mode;

Analyzing the put content DSL to construct a rendering product for rendering the specified dom element;

configuring a release strategy and establishing release association relationship data;

Rendering the release content according to the release strategy and the release association relation data.

The further technical scheme is as follows: the labeling the put-in area in the page according to the registration request comprises the following steps:

and adding a unique identification code to the dom element of the corresponding put-in area in the registration request.

The further technical scheme is as follows: the generating the delivery content DSL with layout information by the rasterization layout dragging mode comprises the following steps:

configuring the release content in a visual construction system in a grid layout dragging mode;

And converting the delivered content into the delivered content DSL with layout information.

The further technical scheme is as follows: the delivery content DSL comprises meta information of each component in the delivery content, position information of each component in the delivery content and size information of each component in the delivery content.

The further technical scheme is as follows: the parsing the delivered content DSL to construct a rendering product that renders the specified dom element includes:

Converting the put content DSL into an abstract syntax tree;

compiling the abstract syntax tree into a code character string, and writing the code character string into an index. Vue file;

taking the index. Vue file as vue project entry file; selecting a node of an entry dom element from the vue item entry file, and modifying the unique identification code node to obtain vue application engineering;

and constructing the vue application engineering packaging into a rendering product.

The further technical scheme is as follows: the delivery association relationship data comprises a delivery number, a unique identification code of a delivery area, a storage address of a rendering product and a delivery strategy number.

The further technical scheme is as follows: rendering the delivery content according to the delivery strategy and the delivery association relationship data comprises the following steps:

Acquiring a request for searching products generated when a user accesses a release page;

screening the address of the rendering product from the delivery association relationship data according to the request to obtain a screening result;

and loading the rendering product in html according to the screening result to render the put content.

The invention also provides a page dynamic throwing device, which comprises:

a registration request acquisition unit configured to acquire a registration request;

the region marking unit is used for marking the put-in region in the page according to the registration request;

A DSL generating unit for generating a delivery content DSL with layout information by a rasterization layout dragging mode;

The analyzing unit is used for analyzing the put content DSL to construct a rendering product for rendering the specified dom element;

The configuration unit is used for configuring the release strategy and establishing release association relationship data;

And the rendering unit is used for rendering the release content according to the release strategy and the release association relationship data.

The invention also provides a computer device which comprises a memory and a processor, wherein the memory stores a computer program, and the processor realizes the method when executing the computer program.

The present invention also provides a storage medium storing a computer program which, when executed by a processor, implements the above method.

Compared with the prior art, the invention has the beneficial effects that: according to the method, the delivery content is built in a visual mode of grid layout through marking the delivery area in the page, the rendering product is built, after the delivery strategy is combined, the hit rendering product is queried at the terminal, the delivery content is dynamically rendered, the grid building system is matched with rich components, different delivery contents can be generated, the problem that template limitation and configuration in the prior art are not visual is solved, the support of self-defined delivery content, self-defined delivery strategy and real-time change of the delivery content are realized, and invasive modification of a service system is not needed.

The invention is further described below with reference to the drawings and specific embodiments.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic diagram of an application scenario of a page dynamic delivery method provided by an embodiment of the present invention;

FIG. 2 is a schematic flow chart of a method for dynamically delivering pages according to an embodiment of the present invention;

FIG. 3 is a schematic sub-flowchart of a method for dynamically delivering pages according to an embodiment of the present invention;

FIG. 4 is a schematic sub-flowchart of a method for dynamically delivering pages according to an embodiment of the present invention;

FIG. 5 is a schematic sub-flowchart of a method for dynamically delivering pages according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of a drop region in a markup page according to an embodiment of the present invention;

fig. 7 is a schematic diagram of generating a delivery content DSL with layout information according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of release association data provided by an embodiment of the present invention;

FIG. 9 is a schematic block diagram of a page dynamic delivery device provided by an embodiment of the present invention;

Fig. 10 is a schematic block diagram of a computer device according to an embodiment of the present invention.

Detailed Description

The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

It should be understood that the terms "comprises" and "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It should be further understood that the term "and/or" as used in the present specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.

Referring to fig. 1 and fig. 2, fig. 1 is a schematic view of an application scenario of a page dynamic delivery method according to an embodiment of the present invention. Fig. 2 is a schematic flow chart of a page dynamic delivery method provided by an embodiment of the present invention. The page dynamic delivery method is applied to the server. The server comprises a server side and a visual construction system, wherein the visual construction system mainly comprises 3 modules: the components warehouse module, canvas module, data configuration module, first, the components warehouse module provides a wide variety of components, which can be card components, picture components, text components, diagram components, etc., which can be dragged into the canvas module. In the canvas module, the location of the component in the canvas may be moved, the size of the component changed, or the component removed from the canvas. And the data configuration module is used for configuring the display data of the current component, such as the text component can configure the displayed text content. Through the visual construction mode, rich release contents can be constructed by combining different assemblies, and release effects can be seen in real time, and the method is realized. The server performs data interaction with the terminal, marks a delivery area in a page in a service system, builds delivery contents in a grid layout visual mode, builds a rendering product, and queries the hit rendering product in a client after combining with a delivery strategy to dynamically render the delivery contents. The rasterized building system is matched with rich components, different throwing contents can be generated, and the problems of template limitation and non-visual configuration in the prior art are solved. The independent rendering products constructed by marking the put areas and combining DSL (domain specific language ) solve the invasiveness problem and universality problem of the prior art on the data logic of the service system.

Fig. 2 is a flow chart of a method for dynamically delivering pages according to an embodiment of the present invention. As shown in fig. 2, the method includes the following steps S110 to S160.

S110, acquiring a registration request.

In this embodiment, the registration request is a request to register the delivery area, and the server generates a unique identification code after receiving the registration request, and then records and returns the identification code.

S120, labeling the put-in area in the page according to the registration request.

In this embodiment, a unique identification code is added to the dom element of the corresponding drop zone in the registration request.

Referring to fig. 6, in the front page of the service system, a unique identifier is added to the dom (document object model ) element of the drop area, where the purpose of adding the unique identifier is to correctly find the rendered entry element when rendering is performed, js (JavaScript) file.

Specifically, the unique identification code can be generated by a uuid technical means; labeling of the drop zone may be achieved by setting the id attribute value of the dom element as a unique identification code.

S130, generating the delivery content DSL with layout information through a rasterization layout dragging mode.

In this embodiment, the delivered content DSL includes meta information of each component in the delivered content, location information of each component in the delivered content, and size information of each component in the delivered content.

In one embodiment, referring to fig. 3, the step S130 may include steps S131 to S132.

S131, configuring the release content in a grid layout dragging mode in the visual construction system.

In this embodiment, the delivery content refers to content presented on a delivery page.

S132, converting the delivery content into delivery content DSL with layout information.

In this embodiment, the delivered content is configured in the visual construction system by way of grid layout drag, and then converted into DSL to describe the delivered content.

Specifically, as shown in fig. 7, the logic for generating DSL in the visualization building system is as follows, initializing JSON (JSON object profile, javaScript Object Notation) data object of one canvas, which has components properties. The Components attribute is an array of json type data format that describes all the component information in the current view. When a new component is dragged into the canvas, json data of the dragged component is added into the current components attribute, and similarly, the position or the size of the component is adjusted in the canvas, the corresponding layout attribute in the json of the component is updated, and when the data attribute of the component is configured, the corresponding properties attribute in the json of the component is updated. The data of component json contains attributes: componentId attributes represent the id of the current component, componentName attributes represent the name of the current component, componentDesc attributes represent the description of the current component, name attributes represent the Chinese name of the current component, className attributes represent the class name of the current component in the component repository, version attributes represent the version number of the current component, and layout attributes represent the position information and size information of the current component in the rasterized layout. Properties attributes represent data attributes of the current component.

The grid layout mode is a minimum dragging unit with a designated width and height. Width rasterization is to divide each line in the canvas into 24 grids equally, and the component can only be dragged into an integer grid in 24 grids when being dragged. The height rasterization is to define a unit height of 30px, and can only drag the height to an integer multiple, such as 60px,90px, each time the component height is adjusted. By using the grid scheme, the dragging operation is more convenient and faster, and different screens can be automatically adapted during the throwing operation.

In this embodiment, DSL is a programming language specifically designed to solve a problem in a certain field, and its syntax and expression capability are relatively simple, so that non-professional developers can perform programming.

And S140, analyzing the put content DSL to construct a rendering product for rendering the specified dom element.

In this embodiment, the rendering product is a product after rendering of the content in the delivery area.

In one embodiment, referring to fig. 4, the step S140 may include steps S141 to S144.

S141, converting the put content DSL into an abstract syntax tree;

In this embodiment, the abstract syntax tree refers to a syntax tree formed by parsing the delivered content DSL and converting each content obtained by parsing into an element corresponding to the syntax tree.

Specifically, firstly, the DSL data which are configured at present are taken in a server through scripts, component data in the DSL data are read and analyzed one by one, each component data is converted into basicJSXElement in an abstract syntax tree, the className in the component data is converted into openingElement and closingElement in abstract syntax tree elements, the properties data in the component data are converted into jsxAttribute in the abstract syntax tree, the layout attribute is specially used as the attribute of a grid layout element in the abstract syntax tree, and other description contents in the component are converted into corresponding mapping data in the abstract syntax tree. After all content parsing in the delivered content DSL file is completed a complete abstract syntax tree is formed,

S142, compiling the abstract syntax tree into a code character string, and writing the code character string into an index.

S143, taking the index. Vue file as a vue project entry file; selecting a node of an entry dom element from the vue item entry file, and modifying the unique identification code node to obtain vue application engineering;

S144, packaging and constructing the vue application engineering into a rendering product.

In this embodiment, invoking the compiling capability of the abstract syntax tree generates a code string, writes an index. Vue file, then uses the index. Vue file as an entry file of item vue, and modifies the node of the entry file of item vue, which selects the entry dom element, into the unique identifier node set in step S120. Finally, this vue application engineering package is built as a front-end rendering product by webpack, which includes: a js (JavaScript) file of rendered DOM structure, a css (Cascading Style Sheets) file of rendered DOM style, and other static artifacts. After the rendering products are constructed, the rendering products are stored and taken to a storage address, and the storage address is saved in a database.

In this embodiment, when a rendering product is constructed, a unique product number is generated, and the rendering product is named by the unique product number, so that the uniqueness is ensured when the association relationship between the product address and the input association relationship data is bound. In storing the rendering product, the rendering product may be stored by MinIO high-performance distributed object storage systems.

S150, configuring a release strategy and establishing release association relation data.

In this embodiment, the delivery policy refers to a series of combinations of policy items that hit the user in the service system. Such as user gender, user age, client type, region of interest, time, etc., are referred to as policy terms, and one or more policy terms are combined into a delivery policy, such as a male user aged 18 years over may be combined into one delivery policy.

As shown in fig. 8, the delivery association relationship data includes a delivery number, a unique identification code of a delivery area, a storage address of a rendering product, and a delivery policy number.

Specifically, each configured policy has a unique number, and then a piece of release association relationship data is established, wherein the release association relationship data is associated with the following contents: the drop zone element unique identifier in step S120, the render product storage address in step S140, and the drop policy number configured in current step S150. After the putting association relationship data is established, the putting association relationship data is stored in a database.

And S160, rendering the release content according to the release strategy and the release association relationship data.

In one embodiment, referring to fig. 5, the step S160 may include steps S161 to S163.

S161, acquiring a request for searching products generated when a user accesses the release page.

In this embodiment, the request refers to a request that the terminal initiates a query for a rendering product to the server when rendering the put element dom.

S162, the address of the rendering product is screened from the throwing association relation data according to the request, so that a screening result is obtained.

In this embodiment, the screening result refers to that the information of the current access user and the unique identification code of the DOM of the current delivery area screen data with the consistent unique identification code from the delivery association relationship data, so as to determine the address of the rendering product.

S163, loading the rendering products in the html according to the screening result to render the put content.

Specifically, when the DOM element of the drop region is rendered in the terminal browser, a back-end interface is used to query which rendering product the current user hits. Then loading the hit rendering product in html (hypertext markup language, hyperText Markup Language,) and automatically rendering the DOM element of the drop region as hit drop content by js in the rendering product after loading is completed.

The server interface queries the rendering product logic hit by the current user, that is, when the terminal renders the delivery element DOM, it will initiate a request for querying the rendering product to the server, the server will use the information of the current access user and the unique identification code of the DOM of the current delivery area to screen in the delivery association relationship data stored in step S150, firstly, screen out the delivery association relationship data matching with the unique identification code of the delivery area element, where there may be a plurality of data, then in the screening result, find the delivery strategy to hit the delivery association relationship data of the current user, where there may be a plurality of data, then find one delivery association relationship data with the highest strategy priority in the screening result, and finally find the corresponding storage address of the rendering product in the data and return the address data.

Wherein, loading the rendering product in html according to the filtering result means that script tags and css tags are generated in html through js grammar. The address attribute of the script tag is set to the storage address of the render product js file, and the address attribute of the css tag is set to the storage address of the render product css file. The browser will then automatically load the rendering product.

According to the page dynamic delivery method, the delivery content is built in a visual mode of grid layout through marking the delivery area in the page, the rendering product is constructed, after the delivery strategy is combined, the hit rendering product is inquired at the terminal, the delivery content is dynamically rendered, the grid building system is matched with rich components, different delivery contents can be generated, the problem that the template limit and configuration in the prior art are not visual is solved, the support of self-defining delivery content, the self-defining delivery strategy and the real-time change of the delivery content are realized, and the invasive modification of a service system is not needed.

Fig. 9 is a schematic block diagram of a page dynamic delivery device 300 provided in an embodiment of the present invention. As shown in fig. 9, the present invention further provides a page dynamic delivery device 300 corresponding to the above page dynamic delivery method. The page dynamic putting apparatus 300 includes a unit for performing the above-described page dynamic putting method, and may be configured in a server. Specifically, referring to fig. 9, the page dynamic delivery apparatus 300 includes a registration request acquiring unit 301, a region marking unit 302, a DSL generating unit 303, a parsing unit 304, a configuration unit 305, and a rendering unit 306.

A registration request acquisition unit 301 configured to acquire a registration request; the area marking unit 302 is configured to mark a delivery area in a page according to the registration request; a DSL generating unit 303, configured to generate a delivery content DSL with layout information by using a rasterized layout dragging manner; a parsing unit 304, configured to parse the delivered content DSL to construct a rendering product for rendering the specified dom element; a configuration unit 305, configured to configure a delivery policy, and establish delivery association relationship data; and the rendering unit 306 is configured to render the delivery content according to the delivery policy and the delivery association relationship data.

In an embodiment, the area marking unit 302 is configured to add a unique identifier to a dom element of the corresponding drop area in the registration request.

In an embodiment, the DSL generating unit 303 includes a content configuration subunit and a conversion subunit.

The content configuration subunit is used for configuring the released content in the visual construction system in a grid layout dragging mode; and the conversion subunit is used for converting the release content into release content DSL with layout information.

In one embodiment, the parsing unit 304 includes a tree formation subunit, a writing subunit, a modification subunit, and a packaging subunit.

A tree formation subunit for converting the delivered content DSL into an abstract syntax tree; a writing subunit, configured to compile the abstract syntax tree into a code string, and write the code string into an index. A modification subunit, configured to use the index. Vue file as a vue item entry file; selecting a node of an entry dom element from the vue item entry file, and modifying the unique identification code node to obtain vue application engineering; and the packing subunit is used for constructing the vue application engineering packing into a rendering product.

In one embodiment, the rendering unit 306 includes a request acquisition subunit, a screening subunit, and a loading subunit

The request acquisition subunit is used for acquiring a request for searching the product generated when the user accesses the release page; a screening subunit, configured to screen an address of a rendering product from the delivery association relationship data according to the request, so as to obtain a screening result; and the loading subunit is used for loading the rendering product in the html according to the screening result so as to render the put content.

It should be noted that, as a person skilled in the art can clearly understand, the specific implementation process of the page dynamic delivery device 300 and each unit may refer to the corresponding description in the foregoing method embodiment, and for convenience and brevity of description, the description is omitted here.

The page dynamic delivery apparatus 300 described above may be implemented in the form of a computer program that can be run on a computer device as shown in fig. 10.

Referring to fig. 10, fig. 10 is a schematic block diagram of a computer device according to an embodiment of the present application. The computer device 500 may be a server, where the server may be a stand-alone server or may be a server cluster formed by a plurality of servers.

With reference to FIG. 10, the computer device 500 includes a processor 502, memory, and a network interface 505 connected by a system bus 501, where the memory may include a non-volatile storage medium 503 and an internal memory 504.

The non-volatile storage medium 503 may store an operating system 5031 and a computer program 5032. The computer program 5032 includes program instructions that, when executed, cause the processor 502 to perform a page dynamic rendering method.

The processor 502 is used to provide computing and control capabilities to support the operation of the overall computer device 500.

The internal memory 504 provides an environment for the execution of a computer program 5032 in the non-volatile storage medium 503, which computer program 5032, when executed by the processor 502, causes the processor 502 to perform a page dynamic placement method.

The network interface 505 is used for network communication with other devices. It will be appreciated by those skilled in the art that the structure shown in FIG. 10 is merely a block diagram of some of the structures associated with the present inventive arrangements and does not constitute a limitation of the computer device 500 to which the present inventive arrangements may be applied, and that a particular computer device 500 may include more or fewer components than shown, or may combine certain components, or may have a different arrangement of components.

Wherein the processor 502 is configured to execute a computer program 5032 stored in a memory to implement the steps of:

Acquiring a registration request; marking a put-in area in a page according to the registration request; generating a delivery content DSL with layout information in a rasterization layout dragging mode; analyzing the put content DSL to construct a rendering product for rendering the specified dom element; configuring a release strategy and establishing release association relationship data; rendering the release content according to the release strategy and the release association relation data.

The delivery association relationship data comprises a delivery number, a unique identification code of a delivery area, a storage address of a rendering product and a delivery strategy number.

In an embodiment, when implementing the step of annotating the drop area in the page according to the registration request, the processor 502 specifically implements the following steps:

and adding a unique identification code to the dom element of the corresponding put-in area in the registration request.

In one embodiment, when implementing the step of generating the delivered content DSL with layout information by using the rasterized layout dragging manner, the processor 502 specifically implements the following steps:

Configuring the release content in a visual construction system in a grid layout dragging mode; and converting the delivered content into the delivered content DSL with layout information.

The delivery content DSL comprises meta information of each component in the delivery content, position information of each component in the delivery content and size information of each component in the delivery content.

In one embodiment, when implementing the step of parsing the delivered content DSL to construct a rendering product for rendering the specified dom element, the processor 502 specifically implements the following steps:

Converting the put content DSL into an abstract syntax tree; compiling the abstract syntax tree into a code character string, and writing the code character string into an index. Vue file; taking the index. Vue file as vue project entry file; selecting a node of an entry dom element from the vue item entry file, and modifying the unique identification code node to obtain vue application engineering; and constructing the vue application engineering packaging into a rendering product.

In an embodiment, when the step of rendering the delivery content according to the delivery policy and the delivery association data is implemented by the processor 502, the following steps are specifically implemented:

Acquiring a request for searching products generated when a user accesses a release page; screening the address of the rendering product from the delivery association relationship data according to the request to obtain a screening result; and loading the rendering product in html according to the screening result to render the put content.

It should be appreciated that in embodiments of the present application, the processor 502 may be a central processing unit (Central Processing Unit, CPU), the processor 502 may also be other general purpose processors, digital signal processors (DIGITAL SIGNAL processors, DSPs), application SPECIFIC INTEGRATED Circuits (ASICs), off-the-shelf programmable gate arrays (Field-programmable GATE ARRAY, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. Wherein the general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

Those skilled in the art will appreciate that all or part of the flow in a method embodying the above described embodiments may be accomplished by computer programs instructing the relevant hardware. The computer program comprises program instructions, and the computer program can be stored in a storage medium, which is a computer readable storage medium. The program instructions are executed by at least one processor in the computer system to implement the flow steps of the embodiments of the method described above.

Accordingly, the present invention also provides a storage medium. The storage medium may be a computer readable storage medium. The storage medium stores a computer program which, when executed by a processor, causes the processor to perform the steps of:

Acquiring a registration request; marking a put-in area in a page according to the registration request; generating a delivery content DSL with layout information in a rasterization layout dragging mode; analyzing the put content DSL to construct a rendering product for rendering the specified dom element; configuring a release strategy and establishing release association relationship data; rendering the release content according to the release strategy and the release association relation data.

The delivery association relationship data comprises a delivery number, a unique identification code of a delivery area, a storage address of a rendering product and a delivery strategy number.

In one embodiment, when the processor executes the computer program to implement the step of annotating the drop area in the page according to the registration request, the processor specifically implements the following steps:

and adding a unique identification code to the dom element of the corresponding put-in area in the registration request.

In an embodiment, when the processor executes the computer program to implement the step of generating the delivered content DSL with layout information by means of the rasterized layout dragging mode, the following steps are specifically implemented:

Configuring the release content in a visual construction system in a grid layout dragging mode; and converting the delivered content into the delivered content DSL with layout information.

The delivery content DSL comprises meta information of each component in the delivery content, position information of each component in the delivery content and size information of each component in the delivery content.

In one embodiment, when the processor executes the computer program to implement the step of parsing the delivered content DSL to construct a rendering product for rendering the specified dom element, the processor specifically implements the steps of:

Converting the put content DSL into an abstract syntax tree; compiling the abstract syntax tree into a code character string, and writing the code character string into an index. Vue file; taking the index. Vue file as vue project entry file; selecting a node of an entry dom element from the vue item entry file, and modifying the unique identification code node to obtain vue application engineering; and constructing the vue application engineering packaging into a rendering product.

In an embodiment, when the processor executes the computer program to implement the step of rendering the delivery content according to the delivery policy and the delivery association data, the method specifically includes the following steps:

Acquiring a request for searching products generated when a user accesses a release page; screening the address of the rendering product from the delivery association relationship data according to the request to obtain a screening result; and loading the rendering product in html according to the screening result to render the put content.

The storage medium may be a U-disk, a removable hard disk, a Read-Only Memory (ROM), a magnetic disk, or an optical disk, or other various computer-readable storage media that can store program codes.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein may be embodied in electronic hardware, in computer software, or in a combination of the two, and that the elements and steps of the examples have been generally described in terms of function in the foregoing description to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

In the several embodiments provided by the present invention, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of each unit is only one logic function division, and there may be another division manner in actual implementation. For example, multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed.

The steps in the method of the embodiment of the invention can be sequentially adjusted, combined and deleted according to actual needs. The units in the device of the embodiment of the invention can be combined, divided and deleted according to actual needs. In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The integrated unit may be stored in a storage medium if implemented in the form of a software functional unit and sold or used as a stand-alone product. Based on such understanding, the technical solution of the present invention is essentially or a part contributing to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a terminal, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention.

While the invention has been described with reference to certain preferred embodiments, it will be understood by those skilled in the art that various changes and substitutions of equivalents may be made and equivalents will be apparent to those skilled in the art without departing from the scope of the invention. Therefore, the protection scope of the invention is subject to the protection scope of the claims.

Claims (10)

1. The page dynamic delivery method is characterized by comprising the following steps:

Acquiring a registration request;

marking a put-in area in a page according to the registration request;

Generating a delivery content DSL with layout information in a rasterization layout dragging mode;

Analyzing the put content DSL to construct a rendering product for rendering the specified dom element;

configuring a release strategy and establishing release association relationship data;

Rendering the release content according to the release strategy and the release association relation data.

2. The method for dynamically delivering pages according to claim 1, wherein labeling the delivery area in the page according to the registration request comprises:

and adding a unique identification code to the dom element of the corresponding put-in area in the registration request.

3. The method for dynamically delivering pages according to claim 1, wherein the generating the delivered content DSL with layout information by using a rasterized layout drag manner includes:

configuring the release content in a visual construction system in a grid layout dragging mode;

And converting the delivered content into the delivered content DSL with layout information.

4. A page dynamic delivery method as claimed in claim 3, wherein the delivery content DSL comprises meta information of each component in the delivery content, location information of each component in the delivery content, and size information of each component in the delivery content.

5. The page dynamic delivery method of claim 1, wherein the parsing the delivery content DSL to construct a rendering product that renders the specified dom element comprises:

Converting the put content DSL into an abstract syntax tree;

compiling the abstract syntax tree into a code character string, and writing the code character string into an index. Vue file;

taking the index. Vue file as vue project entry file; selecting a node of an entry dom element from the vue item entry file, and modifying the unique identification code node to obtain vue application engineering;

and constructing the vue application engineering packaging into a rendering product.

6. The page dynamic delivery method according to claim 1, wherein the delivery association relationship data comprises a delivery number, a unique identification code of a delivery area, a storage address of a rendering product, and a delivery policy number.

7. The method for dynamically delivering pages according to claim 1, wherein the rendering the delivered content according to the delivery policy and the delivery association data comprises:

Acquiring a request for searching products generated when a user accesses a release page;

screening the address of the rendering product from the delivery association relationship data according to the request to obtain a screening result;

and loading the rendering product in html according to the screening result to render the put content.

8. Page dynamic delivery device, its characterized in that includes:

a registration request acquisition unit configured to acquire a registration request;

the region marking unit is used for marking the put-in region in the page according to the registration request;

A DSL generating unit for generating a delivery content DSL with layout information by a rasterization layout dragging mode;

The analyzing unit is used for analyzing the put content DSL to construct a rendering product for rendering the specified dom element;

The configuration unit is used for configuring the release strategy and establishing release association relationship data;

And the rendering unit is used for rendering the release content according to the release strategy and the release association relationship data.

9. A computer device, characterized in that it comprises a memory on which a computer program is stored and a processor which, when executing the computer program, implements the method according to any of claims 1-7.

10. A storage medium storing a computer program which, when executed by a processor, implements the method of any one of claims 1 to 7.