CN105516333B - A kind of web-based exchange method and system - Google Patents

Abstract

An embodiment of the present invention provides a kind of web-based exchange methods and system, this method to include：Web document is used to load webpage in the client；When reading interface element mark from the web document, the interface element is asked to identify corresponding interface element to server；The interface element is loaded in the webpage；When detecting action event on the interface element, an operation requests are generated according to the action event；The interface for calling Service Component, the Service Component that the operation requests are sent to server carry out business processing.The embodiment of the present invention realizes the multiplexing of the fine granularity of module, and module is realized by configuring, and substantially increases the simplicity of update module, greatly reduces the workload of update module.

Description

A webpage-based interactive method and system

technical field

The invention relates to the field of communication technology, in particular to a webpage-based interactive method and a webpage-based interactive system.

Background technique

The rapid development of the network has brought people into the era of information society and network economy, and has had a profound impact on the development of enterprises and personal life.

In order to efficiently process massive amounts of data on the network, modularization is created in the data processing process, which is a specification for decomposing complex objects. For example, decomposing a web page into multiple small blocks, this behavior is modularization .

Each module completes a specific sub-function, and all modules are assembled in a certain way to form a whole to complete the functions required by the entire system.

A module has the following basic attributes: interface, function, logic, and state. Function, state, and interface reflect the external characteristics of the module, and logic reflects its internal characteristics.

However, the website often exits many activities for users to increase the interaction with users. In order to attract users, activities are generally not restarted. Therefore, frequent update activities make the modules of the webpage need to be updated frequently, and the workload is heavy.

Contents of the invention

In view of the above problems, the present invention is proposed to provide a webpage-based interaction method and a corresponding webpage-based interaction system that overcome the above-mentioned problems or at least partially solve the above-mentioned problems.

According to one aspect of the present invention, a webpage-based interaction method is provided, including:

Loading a webpage with a webpage document in the client;

When the interface element identifier is read from the webpage document, requesting the interface element corresponding to the interface element identifier from the server;

loading the interface element in the webpage;

When an operation event is detected on the interface element, an operation request is generated according to the operation event;

The interface of the business component is called, and the operation request is sent to the business component of the server for business processing.

Optionally, the interface element identifier includes an interface element frame identifier and an interface element content identifier;

The step of requesting the server for the interface element corresponding to the interface element identifier includes:

Requesting the interface element frame corresponding to the interface element frame identifier from the server;

Requesting the interface element content corresponding to the interface element content identifier from the server.

Optionally, the step of loading the interface element in the webpage includes:

loading the interface element frame at a specified location in the webpage;

Load the interface element content in the interface element frame.

Optionally, also include:

determining in the server the webpage that triggers the operation request;

Querying configuration parameters corresponding to the webpage;

Call the business component corresponding to the interface, and perform business processing according to the configuration parameters.

Optionally, also include:

Return the result of business processing to the client.

Optionally, also include:

Query the loading method corresponding to the result of business processing in the client;

Load the result of business processing according to the loading method.

According to another aspect of the present invention, a webpage-based interactive system is provided, the system includes a client, and the client includes:

A webpage loading module, suitable for loading a webpage by using a webpage document;

The interface element request module is adapted to request the server for the interface element corresponding to the interface element identifier when the interface element identifier is read from the webpage document;

an interface element loading module, adapted to load the interface element in the webpage;

An operation request generation module, adapted to generate an operation request according to the operation event when an operation event is detected on the interface element;

The interface calling module is adapted to call the interface of the business component, and send the operation request to the business component of the server for business processing.

Optionally, the interface element identifier includes an interface element frame identifier and an interface element content identifier;

The interface element request module is also adapted to:

Requesting the interface element frame corresponding to the interface element frame identifier from the server;

Requesting the interface element content corresponding to the interface element content identifier from the server.

Optionally, the interface element loading module is also suitable for:

loading the interface element frame at a specified location in the webpage;

Load the interface element content in the interface element frame.

Optionally, the system also includes a server, and the server includes:

A web page determining module, adapted to determine the web page that triggers the operation request;

A configuration parameter query module, adapted to query configuration parameters corresponding to the webpage;

The business component calling module is adapted to call the business component corresponding to the interface, and perform business processing according to the configuration parameters.

Optionally, the server also includes:

The result returning module is suitable for returning the result of business processing to the client.

Optionally, the customer degree also includes:

The loading method query module is suitable for querying the loading method corresponding to the result of business processing in the client;

The result loading module is adapted to load the result of business processing according to the loading method.

The embodiment of the present invention adopts the method of separating the front and back ends, separates the form of the module from the function of the module, loads the interface elements at the front end, and transfers the operation request to the back end for business processing through the interface of the business component, realizing The fine-grained multiplexing of modules realizes modules through configuration, which greatly improves the simplicity of updating modules and greatly reduces the workload of updating modules.

In the embodiment of the present invention, the function of the control module is realized by configuring parameters, which further improves the simplicity of updating the module and reduces the workload of the updating module while ensuring the security of communication.

The above description is only an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention, it can be implemented according to the contents of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and understandable , the specific embodiments of the present invention are enumerated below.

Description of drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiment. The drawings are only for the purpose of illustrating a preferred embodiment and are not to be considered as limiting the invention. Also throughout the drawings, the same reference numerals are used to designate the same parts. In the attached picture:

FIG. 1 shows a flow chart of steps in Embodiment 1 of a webpage-based interaction method according to an embodiment of the present invention;

FIG. 2 shows a flow chart of steps in Embodiment 2 of a webpage-based interaction method according to an embodiment of the present invention; and

Fig. 3 shows a structural block diagram of an embodiment of a webpage-based interactive system according to an embodiment of the present invention.

Detailed ways

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided for more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

Referring to FIG. 1 , it shows a flow chart of the steps of Embodiment 1 of a webpage-based interactive method according to an embodiment of the present invention, which may specifically include the following steps:

Step 101, using a webpage document to load a webpage in the client;

In a specific implementation, the client may send a web page request to the server to load the corresponding web page.

The page loading request may refer to an instruction sent by the client to load a certain page.

For example, a user may request to load a web page by clicking a link in a browser, or start a game client, open a home page, and so on.

When a user clicks on a link, it is equivalent to receiving a loading request for a web page; similarly, when the game client is started, it is equivalent to receiving a loading request for loading a web page.

Wherein, the content of the loading request may include the identification of the webpage that the user requests to load and/or the characteristics of the webpage.

The webpage identifier can be information that can represent a uniquely determined webpage, such as a Uniform Resource Identifier (Uniform Resource Identifier, URI), and the Uniform Resource Identifier can specifically include a Uniform Resource Locator (Uniform Resource Locator, URL), or a Uniform Resource Identifier. Name (Uniform Resource Name, URN) and so on.

The client uses DNS (Domain Name System, Domain Name Resolution System) to resolve and find the IP (Internet Protocol, a protocol for interconnection between networks) address mapped to the domain name (Domain Name) in the URL of the webpage.

After successfully obtaining the IP address, the client can request a connection to the server where the IP address is located. After successfully connecting to the server with the IP address, the client can initiate a web page loading request to the server with the IP address through the HTTP (Hypertexttransfer protocol, Hypertext Transfer Protocol) protocol.

After receiving the request, the server waits for processing, and finally returns a response to the client.

At this time, under the HTTP protocol, the client may receive an HTML (Hypertext MarkupLanguage, Hypertext Markup Language) type document from the server.

The client can parse HTML documents to generate tree-structured objects, that is, DOM (Document Object Model, Document Object Model). Each object is a node on the DOM, and these objects can represent web resources such as text and pictures.

The client can start to display this HTML document and obtain the addresses of the embedded page resources, and then the client initiates a request to the server to obtain these page resources and display them in the client's HTML document.

Step 102, when the interface element identifier is read from the webpage document, request the server for the interface element corresponding to the interface element identifier;

In the embodiment of the present invention, the module may be loaded in a manner of separating the front and back ends, that is, the front end displays UI (User Interface, user interface) elements, and the back end performs business processing.

In the webpage document, the interface element identifier of the module can be written in advance, and when the interface element identifier is read, a request can be made to the server for the interface element corresponding to the interface element identifier.

Wherein, the interface element identifier may be information that can represent a uniquely determined interface element, for example, an interface element ID.

In one request mode, the interface element is a whole, and the entire interface element can be directly requested.

In another request method, the interface element is a combination, that is, split into interface element frame and interface element content.

Specifically, the interface element identifier may include an interface element frame identifier and an interface element content identifier.

Wherein, the interface element frame identifier may be information that can represent a uniquely determined interface element frame, for example, an interface element frame ID.

The interface element content identifier may be information that can represent a uniquely determined interface element content, for example, an interface element content ID.

Therefore, during loading, the interface element frame corresponding to the interface element frame identifier may be requested from the server, and the interface element content corresponding to the interface element content identifier may be requested from the server.

Taking the lottery module as an example, the interface of the lottery can be displayed on the front end, and the logic of the lottery can be deployed on the back end.

Among them, when displaying on the front end, the style of the lottery can be used, such as the shape of the turntable (such as square, round, etc.), the lottery button, etc., as the frame of the interface element, and the prize of the lottery, such as the picture of the prize, can be used as the content of the interface element .

In actual application, interface elements can be requested to the server based on Ajax (Asynchronous Javascript And XML, asynchronous JavaScript and XML (subset of standard general markup language)).

Ajax is the encapsulation of the browser's own characteristics (IE5.6 browser is ActiveXObject, other browsers are XMLHttpRequest), and it becomes a method. The goal is to send an HTTP (Hypertext transfer protocol, hypertext transfer protocol) request, which generally includes several sections:

url: Requested URL (Uniform Resource Locator, Uniform Resource Locator);

data: request parameters, such as JobID;

timeout: the timeout time, that is, the maximum waiting time from receiving the server response, and the request will be abandoned if the timeout timeout;

success: The processing function that successfully receives the response data;

error: Request various exception handling functions.

Step 103, loading the interface elements in the webpage;

In one loading method, the interface element is a whole, and the entire interface element can be directly loaded.

In another loading method, the interface element is a combination, then the interface element frame can be loaded at a specified position in the web page, and the interface element content can be loaded in the interface element frame, so as to realize the overall loading of the interface elements.

It should be noted that since the interface elements are returned through the interface, the returned data structure is basically fixed, so the front end needs to support the data returned by this interface for different presentations, and the specific display method can be determined by the field The technicians make settings according to the actual situation, as long as the display is supported, which is not limited in the embodiment of the present invention.

Taking the lottery interface as an example, one of the back-end interfaces is the prize information interface, and the returned data structure is fixed, so the front-end must support this interface, so the front-end can be arranged in any style, such as a disc, a square or something more Complicated HTML 5 game results, etc., in various forms.

Step 104, when an operation event is detected on the interface element, generate an operation request according to the operation event;

After the interface element is displayed on the web page, the user can perform operations on the interface element by clicking or other means to generate operation events such as clicking.

When the client detects an operation event on the interface element, it generates an operation request according to the nature of the interface element.

Taking the lottery drawing as an example, after the web page displays the lottery drawing interface, the user can click the "lottery draw" button, and the client can generate a lottery drawing operation request.

Step 105, call the interface of the business component, and send the operation request to the business component of the server for business processing.

In the webpage document, the interface of the business component of the module can be written in advance, and the operation request is sent to the server through the interface, and the business component is called to perform business processing according to the logic defined by it.

Taking lottery drawing as an example, the client calls the interface of the component responsible for lottery drawing, sends the operation request of lottery drawing to the server, and the server calls the component to perform lottery drawing.

In actual application, interface elements can be requested to the server based on Ajax (Asynchronous Javascript And XML, asynchronous JavaScript and XML (subset of standard general markup language)).

The embodiment of the present invention adopts the method of separating the front and back ends, separates the form of the module from the function of the module, loads the interface elements at the front end, and transfers the operation request to the back end for business processing through the interface of the business component, realizing The fine-grained multiplexing of modules realizes modules through configuration, which greatly improves the simplicity of updating modules and greatly reduces the workload of updating modules.

Referring to FIG. 2 , it shows a flow chart of the steps of Embodiment 2 of a webpage-based interaction method according to an embodiment of the present invention, which may specifically include the following steps:

Step 201, using a webpage document to load a webpage in the client;

Step 202, when the interface element identifier is read from the webpage document, request the server for the interface element corresponding to the interface element identifier;

Step 203, loading the interface elements in the webpage;

Step 204, when an operation event is detected on the interface element, generate an operation request according to the operation event;

Step 205, call the interface of the business component, and send the operation request to the business component of the server;

Step 206, determining the webpage that triggers the operation request in the server;

Step 207, querying the configuration parameters corresponding to the webpage;

Step 208, call the business component corresponding to the interface, and perform business processing according to the configuration parameters;

Due to the separation of the front and back ends of the module, in order to prevent the communication from being intercepted and cracked, no configuration parameters are set in the operation request, and basic information such as the web page URL and user ID are reserved.

After receiving the operation request, the server searches the configuration list for configuration parameters corresponding to the URL of the web page in the operation request, and invokes the business component to perform business processing according to the configuration parameters.

Taking the lottery as an example, which webpage (characterized by URL) is set which activity is set in the configuration list, and which configuration parameters are required for this activity, such as lottery pool (prize data), lottery probability, etc.

Call the business component to perform lottery drawing (business processing) according to the configuration parameters.

Step 209, return the result of business processing to the client;

After the business processing is completed, the server returns the processing result of the business component to the client.

Step 210, query the loading method corresponding to the result of business processing in the client;

Step 211, load the result of business processing according to the loading method.

In the embodiment of the present invention, the loading mode of the result can be defined in the configuration list in advance, and after receiving the result of the business processing, it can be displayed according to the loading mode.

Taking the lottery as an example, if the user wins a real item, a pop-up window can be loaded to allow the user to fill in information such as the recipient, recipient address, and contact phone number; if the user wins a virtual item, the drawn virtual item can be displayed directly. thing.

In the embodiment of the present invention, the function of the control module is realized by configuring parameters, which further improves the simplicity of updating the module and reduces the workload of the updating module while ensuring the security of communication.

For the method embodiment, for the sake of simple description, it is expressed as a series of action combinations, but those skilled in the art should know that the embodiment of the present invention is not limited by the described action order, because according to the embodiment of the present invention , certain steps may be performed in other order or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification belong to preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.

Referring to FIG. 3 , it shows a structural block diagram of an embodiment of a webpage-based interactive system according to an embodiment of the present invention. The system includes a client, and the client may specifically include the following modules:

The webpage loading module 301 is suitable for loading a webpage by using a webpage document;

The interface element request module 302 is adapted to request the server for an interface element corresponding to the interface element identifier when the interface element identifier is read from the webpage document;

An interface element loading module 303, adapted to load the interface element in the webpage;

An operation request generation module 304, adapted to generate an operation request according to the operation event when an operation event is detected on the interface element;

The interface calling module 305 is adapted to call the interface of the business component, and send the operation request to the business component of the server for business processing.

In an optional embodiment of the present invention, the interface element identifier includes an interface element frame identifier and an interface element content identifier;

The interface element request module 302 may also be adapted to:

Requesting the interface element frame corresponding to the interface element frame identifier from the server;

Requesting the interface element content corresponding to the interface element content identifier from the server.

In an optional embodiment of the present invention, the interface element loading module 303 may also be adapted to:

loading the interface element frame at a specified location in the webpage;

Load the interface element content in the interface element frame.

In an optional embodiment of the present invention, the system may also include a server, and the server may specifically include the following modules:

A web page determining module, adapted to determine the web page that triggers the operation request;

A configuration parameter query module, adapted to query configuration parameters corresponding to the webpage;

The business component calling module is adapted to call the business component corresponding to the interface, and perform business processing according to the configuration parameters.

In an optional embodiment of the present invention, the server may also include the following modules:

The result returning module is suitable for returning the result of business processing to the client.

In an optional embodiment of the present invention, the customer degree may also include the following modules:

The loading method query module is suitable for querying the loading method corresponding to the result of business processing in the client;

The result loading module is adapted to load the result of business processing according to the loading method.

As for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for the related parts, please refer to the part of the description of the method embodiment.

The algorithms and displays presented herein are not inherently related to any particular computer, virtual system, or other device. Various generic systems can also be used with the teachings based on this. The structure required to construct such a system is apparent from the above description. Furthermore, the present invention is not specific to any particular programming language. It should be understood that various programming languages can be used to implement the content of the present invention described herein, and the above description of specific languages is for disclosing the best mode of the present invention.

In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure the understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, in order to streamline this disclosure and to facilitate an understanding of one or more of the various inventive aspects, various features of the invention are sometimes grouped together in a single embodiment, figure, or its description. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art can understand that the modules in the device in the embodiment can be adaptively changed and arranged in one or more devices different from the embodiment. Modules or units or components in the embodiments may be combined into one module or unit or component, and furthermore may be divided into a plurality of sub-modules or sub-units or sub-assemblies. All features disclosed in this specification (including accompanying claims, abstract and drawings) and any method or method so disclosed may be used in any combination, except that at least some of such features and/or processes or units are mutually exclusive. All processes or units of equipment are combined. Each feature disclosed in this specification (including accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will understand that although some embodiments described herein include some features included in other embodiments but not others, combinations of features from different embodiments are meant to be within the scope of the invention. and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.

The various component embodiments of the present invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art should understand that a microprocessor or a digital signal processor (DSP) may be used in practice to implement some or all functions of some or all components in the webpage-based interactive device according to the embodiment of the present invention. The present invention can also be implemented as an apparatus or an apparatus program (for example, a computer program and a computer program product) for performing a part or all of the methods described herein. Such a program for realizing the present invention may be stored on a computer-readable medium, or may be in the form of one or more signals. Such a signal may be downloaded from an Internet site, or provided on a carrier signal, or provided in any other form.

It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention can be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means can be embodied by one and the same item of hardware. The use of the words first, second, and third, etc. does not indicate any order. These words can be interpreted as names.

Claims (10)

1. A webpage-based interactive method, comprising: Loading a webpage with a webpage document in the client; When the interface element identifier is read from the webpage document, requesting the interface element corresponding to the interface element identifier from the server; loading the interface element in the webpage; When an operation event is detected on the interface element, an operation request is generated according to the operation event; calling the interface of the business component, and sending the operation request to the business component of the server for business processing; Wherein, the steps of performing business processing by the business components of the server include: determining in the server the webpage that triggers the operation request; Querying configuration parameters corresponding to the webpage; Call the business component corresponding to the interface, and perform business processing according to the configuration parameters. 2. The method according to claim 1, wherein the interface element identification comprises an interface element frame identification and an interface element content identification; The step of requesting the server for the interface element corresponding to the interface element identifier includes: Requesting the interface element frame corresponding to the interface element frame identifier from the server; Requesting the interface element content corresponding to the interface element content identifier from the server. 3. The method according to claim 2, wherein the step of loading the interface element in the web page comprises: loading the interface element frame at a specified location in the webpage; Load the interface element content in the interface element frame. 4. The method of claim 1, further comprising: Return the result of business processing to the client. 5. The method of claim 1 or 2 or 3 or 4, further comprising: Query the loading method corresponding to the result of business processing in the client; Load the result of business processing according to the loading method. 6. A web-based interactive system, said system comprising a client, said client comprising: A webpage loading module, suitable for loading a webpage by using a webpage document; The interface element request module is adapted to request the server for the interface element corresponding to the interface element identifier when the interface element identifier is read from the webpage document; an interface element loading module, adapted to load the interface element in the webpage; An operation request generation module, adapted to generate an operation request according to the operation event when an operation event is detected on the interface element; The interface calling module is suitable for calling the interface of the business component, and sending the operation request to the business component of the server for business processing; The system also includes a server, the server including: A web page determining module, adapted to determine the web page that triggers the operation request; A configuration parameter query module, adapted to query configuration parameters corresponding to the webpage; The business component calling module is adapted to call the business component corresponding to the interface, and perform business processing according to the configuration parameters. 7. The system according to claim 6, wherein the interface element identification comprises an interface element frame identification and an interface element content identification; The interface element request module is also adapted to: Requesting the interface element frame corresponding to the interface element frame identifier from the server; Requesting the interface element content corresponding to the interface element content identifier from the server. 8. The system according to claim 7, wherein the interface element loading module is further adapted to: loading the interface element frame at a specified location in the webpage; Load the interface element content in the interface element frame. 9. The system according to claim 6, wherein the server further comprises: The result returning module is suitable for returning the result of business processing to the client. 10. The system according to claim 6 or 7 or 8 or 9, wherein the client further comprises: The loading method query module is suitable for querying the loading method corresponding to the result of business processing in the client; The result loading module is adapted to load the result of business processing according to the loading method.