CN110989987B

CN110989987B - Portal webpage generation method and device, client, server and storage medium

Info

Publication number: CN110989987B
Application number: CN201911229483.1A
Authority: CN
Inventors: 王帅琪
Original assignee: Beijing Xiaomi Mobile Software Co Ltd
Current assignee: Beijing Xiaomi Mobile Software Co Ltd
Priority date: 2019-12-04
Filing date: 2019-12-04
Publication date: 2024-03-01
Anticipated expiration: 2039-12-04
Also published as: CN110989987A

Abstract

The present disclosure relates to a method, a device, a client, a server and a storage medium for generating a portal page, and acquiring component paths of functional modules of the portal page; based on the component path of the functional module, obtaining a routing instance of the functional module, wherein the routing instance comprises: a corresponding relationship of component paths and component identifications; exporting and registering the route instance into a global route configured for the portal page; and generating the portal webpage by accessing the global route. Therefore, the method is convenient for developers to update any functional module or component of the portal webpage, improves the flexibility of the information of the portal webpage, does not need to redevelop the whole webpage, improves the development efficiency, and reduces the development cost.

Description

Portal webpage generation method and device, client, server and storage medium

Technical Field

The disclosure relates to the field of computer technology, and in particular, to a method, a device, a client, a server and a storage medium for generating portal pages.

Background

The portal page is a comprehensive page for displaying various information, in the related technology, one page is usually developed as a project, and resources are also concentrated in the same server, so that the loading of the existing portal page is based on the concentrated loading of the server, and the portal page is used as a special page, because various information is integrated, if the information of the portal page is relatively fixed according to the traditional development and loading modes, the problems of low development efficiency, high development cost and the like are necessarily caused when some kinds of information are required to be replaced, and the dynamic performance of the portal page is low.

Disclosure of Invention

According to a first aspect of an embodiment of the present disclosure, there is provided a method for generating a portal page, applied to a client, including:

acquiring a component path of a functional module of the portal webpage;

based on the component path of the functional module, obtaining a routing instance of the functional module, wherein the routing instance comprises: a corresponding relationship of component paths and component identifications;

exporting and registering the route instance into a global route configured for the portal page;

and generating the portal webpage by accessing the global route.

Optionally, the generating the portal page by accessing the global route includes:

determining the component identification of the routing instance of the function module of the portal page by accessing the global route;

acquiring a component corresponding to the component identifier based on the component identifier;

based on the components, the function module is loaded in the portal page.

Optionally, the acquiring, based on the component identifier, the component corresponding to the component identifier includes:

sending an acquisition request to a component platform according to the component identifier;

And receiving the component corresponding to the component identifier returned by the component platform based on the acquisition request.

if the global route is accessed for the first time, acquiring the component corresponding to the component identifier from a server based on the component identifier, and storing the component in a local area;

or,

and if the global route is not accessed for the first time and the functional module is accessed, acquiring the component corresponding to the component identifier on the basis of the component identifier.

Alternatively, different of the components are deployed with the same software framework.

According to a second aspect of the embodiments of the present disclosure, there is provided a method for generating a portal page, applied to a server, including:

and sending the route instance of the functional module of the portal webpage and/or the component corresponding to the route instance to the client, wherein the route instance comprises: and the routing instance and/or the component corresponding to the routing instance are used for the client to generate the portal webpage.

Optionally, the method further comprises:

Receiving a first access request of the client for the global route of the portal webpage;

the step of sending the route instance of the functional module of the portal webpage and/or the component corresponding to the route instance to the client comprises the following steps:

and based on the first access request, sending the route instance of the functional module of the portal webpage and/or the component corresponding to the route instance to the client.

According to a third aspect of the embodiments of the present disclosure, there is provided a portal page generating apparatus, applied to a client, including:

a first acquisition module configured to acquire component paths of the function modules of the portal page;

a second obtaining module configured to obtain a routing instance of the functional module based on the component path of the module, wherein the routing instance includes: a corresponding relationship of component paths and component identifications;

a registration module configured to export and register the routing instance into a global route that is the portal page;

and the generation module is configured to generate the portal webpage by accessing the global route.

Optionally, the generating module further includes:

a determining sub-module configured to determine the component identification of the routing instance of the functional module of the portal page by accessing the global route;

An acquisition sub-module configured to acquire a component corresponding to the component identifier based on the component identifier;

and a loading sub-module configured to load the function module within the portal page based on the component.

Optionally, the acquiring submodule is further configured to:

or,

According to a fourth aspect of the embodiments of the present disclosure, there is provided a portal page generating apparatus, applied to a server, including:

the sending module is configured to send the routing instance of the functional module of the portal webpage and/or the component corresponding to the routing instance to the client, wherein the routing instance comprises: and the routing instance and/or the component corresponding to the routing instance are used for the client to generate the portal webpage.

Optionally, the apparatus further comprises:

the receiving module is configured to receive a first access request of the client for global routing of the portal page;

the sending module is further configured to send the routing instance of the functional module of the portal webpage and/or the component corresponding to the routing instance to the client based on the first access request.

According to a fifth aspect of embodiments of the present disclosure, there is provided a client, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

acquiring a component path of a functional module of the portal webpage;

and generating the portal webpage by accessing the global route.

According to a sixth aspect of embodiments of the present disclosure, there is provided a server comprising:

a processor;

a memory for storing processor-executable instructions;

Wherein the processor is configured to:

and sending the route instance of the functional module of the portal webpage and/or the component corresponding to the route instance to the client, wherein the route instance comprises: and the route instance and/or the component corresponding to the route instance are used for the client to generate the portal webpage.

According to a fourth aspect of embodiments of the present disclosure, there is provided a non-transitory computer readable storage medium having stored thereon a computer program for execution by a processor to perform any of the method steps described above.

The technical scheme provided by the embodiment of the disclosure can comprise the following beneficial effects:

in the embodiment of the disclosure, the component path of the functional module of the portal webpage is acquired; based on the component path of the functional module, obtaining a routing instance of the functional module, wherein the routing instance comprises: a corresponding relationship of component paths and component identifications; exporting and registering the route instance into a global route configured for the portal page; and generating the portal webpage by accessing the global route. That is, in the embodiment of the disclosure, each functional module in the portal page can be split, even components in the functional module can be split, when the portal page is accessed, the split components are found out to be identified based on each route instance registered to the global route, so that each functional module can be loaded simultaneously or sequentially by accessing the global route corresponding to the component route to generate the portal page. Therefore, the method and the system facilitate the developer to update any functional module or component of the portal page, improve the flexibility of the information of the portal page, further strengthen the dynamic performance of the portal page, and avoid the need of redevelopment of the whole page, improve the development efficiency and reduce the development cost.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.

FIG. 1 is a flowchart illustrating a method of generating a portal page in accordance with an exemplary embodiment;

FIG. 2 is a composition diagram of a portal page shown in accordance with an exemplary embodiment;

FIG. 3 is another flow chart illustrating a method of generating portal pages in accordance with an exemplary embodiment;

FIG. 4 is a further flowchart illustrating a method of portal page generation in accordance with an exemplary embodiment;

FIG. 5 is a further flowchart illustrating a method of portal page generation in accordance with an exemplary embodiment;

FIG. 6 is a further flowchart illustrating a method of portal page generation in accordance with an exemplary embodiment;

FIG. 7 is a flowchart illustrating a method of generating a portal page in accordance with another exemplary embodiment;

FIG. 8 is a block diagram illustrating a portal page generating apparatus in accordance with an exemplary embodiment;

FIG. 9 is a block diagram illustrating a portal page generating apparatus according to another exemplary embodiment;

FIG. 10 is a block diagram of a client shown in accordance with an exemplary embodiment;

fig. 11 is a block diagram of a server, according to an example embodiment.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the invention. Rather, they are merely examples of apparatus and methods consistent with aspects of the invention as detailed in the accompanying claims.

Fig. 1 is a flowchart illustrating a method for generating a portal page according to an exemplary embodiment, and the method is applied to a client as shown in fig. 1, and includes the following steps:

step 101: and acquiring the component path of the functional module of the portal webpage.

Here, the client may specifically be a mobile client or a fixed client; the mobile client can be a mobile phone, a tablet computer or a notebook computer; the fixed client can be a desktop computer or intelligent household equipment and the like; the intelligent household equipment can be an intelligent television or an intelligent refrigerator and the like. The method can be applied to any device capable of accessing a web page through a browser.

It will be appreciated that portal pages refer to pages exposed by an application system that channels some type of comprehensive internet information resource and provides the relevant information server.

Referring to fig. 2, fig. 2 is a schematic diagram illustrating the composition of a portal page according to an exemplary embodiment. As shown, the portal page 20 may include one or more function modules 201, where the function modules 201 may be understood as web page modules implementing different functions according to the web pages divided by service type. For example, if the portal page is a web page presented by a management website in an enterprise, the portal page may be divided into different functional modules, such as a human resource management module, a product popularization cooperation module, and the like, according to different service portions. If the portal page is a web page presented by an official website of an enterprise, for example, a messenger, a new wave, etc., the portal page may be divided into different functional modules, such as a video module, a news module, etc., according to different service types.

Further, each functional module 201 may in turn include one or more components 2011.

It is understood that the components are self-contained, programmable, reusable, language-independent software elements. The components can be easily used for assembly in an application. The application program can be run on a component basis or pages corresponding to the components can be loaded.

In this embodiment, each component may be independently developed to be placed under different paths. Here, the step 101 may further include: by accessing the URL (uniform resource locator, uniform resource location system), component paths of the functional modules of the portal page are obtained. The component path here is a routing path that can be read to the corresponding component module.

Step 102: based on the component path of the functional module, obtaining a routing instance of the functional module, wherein the routing instance comprises: correspondence of component paths and component identifications.

It should be understood that a routing path refers to an end-to-end path that is determined as data goes from a source to a destination, and in short, can characterize the path of network data, which maps a URL path with a function. When a different routing path is accessed, a different component is displayed to replace the currently displayed page. Further, the routing configuration may include routing paths and component related information configured for the routing. Here, the routing configuration may be made up of multiple routing instances, with the smallest routing instance including the component path and component identification. Here, the component identification may be used to identify a component, including a name of the component or a number of the component, etc.

Here, the step 102 may include: acquiring a routing configuration from the server based on the component path of the functional module; and determining a routing instance of the functional module according to the routing configuration.

In this embodiment, by obtaining the routing instance, at least the component identifier may be obtained, so that the component may be conveniently found to load the function module, and further generate the portal page.

Step 103: and exporting and registering the route instance into a global route configured for the portal page.

Here, the global route may understand the set of all component paths in the portal page.

Here, the route instance is exported and registered into a global route configured for the portal page, that is, the global route includes all function modules currently in the portal page and component paths of the function modules, and component identifiers corresponding to the component paths, based on the registration of the route instance.

Step 104: and generating the portal webpage by accessing the global route.

Here, the global route includes all current function modules and component paths of the function modules in the portal webpage, and component identifiers corresponding to the component paths, so that all components in the portal webpage can be found by accessing the global route, thereby generating the portal webpage.

In this embodiment, the component path and the component identifier of each functional module of each portal page are obtained by exporting and registering the routing instance of each functional module into the global route configured for the portal page, and accessing the global route of the portal page, so as to find the component to generate the portal page. Therefore, compared with the prior art, the portal webpage is used as an integral development project, and when the portal webpage is loaded, the portal webpage is loaded only through one path, and can not be reasonably split, and in the embodiment, the portal webpage can be split into a plurality of functional modules, even a plurality of components, and the functional modules or the components can be independently developed, so that the development efficiency is improved; when some functional modules or some components of the portal are required to be replaced or upgraded, the corresponding functional modules or components can be only re-developed or upgraded, so that the information of the portal page is replaced more flexibly, the dynamic performance of the portal page is enhanced, the development cost can be reduced, and the development efficiency is improved.

As an alternative embodiment, referring to fig. 3, fig. 3 is another flowchart illustrating an exemplary embodiment, as shown in fig. 3, the generating the portal page by accessing the global route includes:

Step 301: determining the component identification of the routing instance of the function module of the portal page by accessing the global route;

step 302: acquiring a component corresponding to the component identifier based on the component identifier;

step 303: based on the components, the function module is loaded in the portal page.

It will be appreciated that, based on the component identification, a component corresponding to the component identification may be found. The component identification includes the name of the component or the number of the component.

In some embodiments, the component may be stored in a server where the component is obtained based on the component identification.

Here, the server may include one or more servers, and different components may be placed in different servers.

Referring to fig. 4, fig. 4 is a further flowchart illustrating a method for generating a portal page according to an exemplary embodiment, as shown in fig. 4, the method includes:

step 3021: the client sends an access request for accessing the global route to the server;

step 3022: the server returns the component corresponding to the component identifier to the client based on the component identifier;

Step 3023: the client sends an access request for accessing the global route to the server again;

step 3024: the server returns the component corresponding to the component identifier to the client based on the component identifier again.

Here, the components may be respectively developed and deployed in the same or different servers, and the component identifier is parsed based on the access request of the global reason, so as to obtain the components, so as to generate the portal webpage. Because the components can be developed respectively, the development efficiency can be improved, the updating or the replacement of the components is flexible, and the development cost is reduced.

The components are required to be obtained and loaded from the server each time, which necessarily affects the recording speed of the portal page. In other embodiments, in order to increase the loading speed of the portal page, the obtaining, based on the component identifier, the component corresponding to the component identifier may further include:

Or,

Specifically, referring to fig. 5, fig. 5 is a further flowchart illustrating a method for generating a portal page according to an exemplary embodiment, and as shown in fig. 5, the method includes:

step 3026: the client sends an access request for accessing the global route to the server;

step 3027: the server returns the component corresponding to the component identifier to the client based on the component identifier, and stores the component;

step 3028: the client side locally returns the component corresponding to the component identifier to the client side based on the component identifier.

In this embodiment, when the global route is accessed for the first time, the component corresponding to the component identifier may be downloaded and stored locally in advance, and when the global route is accessed again and a certain functional module is accessed next time, the component corresponding to the component identifier may be obtained locally based on the component identifier, so that the loading speed of the component is increased, and thus the overall loading speed of the portal webpage is increased.

In other embodiments, the component may be stored in a component platform in which the component is obtained based on the component identification.

It should be noted that, the component platform may be a platform developed in advance for the provider of the portal page, and the portal page for storing components, where the component platform obtains the components through the component platform, may be adapted to a management website inside the enterprise.

Here, the acquiring, based on the component identifier, the component corresponding to the component identifier includes:

and returning the component corresponding to the component identifier based on the acquisition request based on the component platform.

Specifically, referring to fig. 6, fig. 6 is a further flowchart illustrating a method for generating a portal page according to an exemplary embodiment, and as shown in fig. 6, the method includes:

step 601: the client sends an access request for accessing the global route to the server;

step 602: the server returns a routing instance to the client;

step 603: the client sends an acquisition request to the component platform;

step 604: the component platform returns the component corresponding to the component identifier according to the component identifier corresponding to the component path in the routing instance;

step 605: the client generates a portal page according to the returned components.

In this embodiment, since the components are stored on the component platform, no search is required in the server, and the time for finding the components in a large amount of data in the server is saved, so that the loading speed of the functional module can be increased, and the loading speed of the portal page can be increased. And moreover, the component platform can be managed by a developer of the portal webpage, and when components are replaced or updated, a third party protocol and the like of a server are not needed to be relied on, so that the deployment and the release are more convenient.

It should be added that, the components can be modified, for example, by modifying the identification of the components, that is, the display position of the components on the web page can be modified, so that the portal web page is more dynamic.

In another alternative embodiment, different of the components are deployed with the same software framework.

The software framework refers to a software component specification for realizing a certain industry standard or completing a specific basic task, and is a software product for providing basic functions required by the specification when the software component specification is realized.

The embodiment of the disclosure deploys the same software framework on different components, so that the components can be multiplexed by different functional modules and even different portal pages in the use process. And the same software framework is deployed for different components, so that the components have the same dependence in multiplexing, and the dependence loading can be reduced in reloading, and the loading speed is improved.

Further, since different of the components are deployed with the same software framework, after the state of one of the function modules of the portal page is changed, the state of the function module can be synchronized based on the same software framework. For example, the portal page is a page displayed by a human resource management website inside an enterprise, and the human resource management website includes: and if one of the functional modules is in a login state, the login state can be synchronized based on the same software framework, so that state change operation for accessing other functional modules is reduced, and user experience is improved.

Fig. 7 is a flowchart illustrating a method of generating a portal page according to another exemplary embodiment, which is applied to a server as shown in fig. 7, and includes the steps of:

step 701: and sending the route instance of the functional module of the portal webpage and/or the component corresponding to the route instance to the client.

Here, the routing instance includes: and the routing instance and/or the component corresponding to the routing instance are used for the client to generate the portal webpage.

In this embodiment, the server sends the routing instance of the functional module of the portal page and/or the component corresponding to the routing instance to the client, but does not send the portal page as a whole, that is, in this embodiment, the functional modules, even components, of the portal page can be developed independently of each other, so as to improve the development efficiency; when some functional modules or some components of the portal are required to be replaced or upgraded, the corresponding functional modules or components can be only re-developed or upgraded, so that the information of the portal page is replaced more flexibly, the dynamic performance of the portal page is enhanced, the development cost can be reduced, and the development efficiency is improved.

In an alternative embodiment, the method further comprises:

In this embodiment, after the first access, the routing instance of the function module of the portal page may be sent to the client, and then, the client may find, according to the component identifier in the routing instance, the component corresponding to the component identifier on other platforms, for example, the local or component platform of the client, so that the server does not need to be accessed any more, so that the loading speed may be increased without depending on the network. Even after the first access, the components corresponding to the routing instance are sent to the client, so that the components are directly obtained locally without passing through other platforms when the next access is performed, and obviously, the loading speed can be improved without depending on a network.

Further, the present disclosure further provides a specific embodiment, so as to further understand the method for generating the portal page provided by the embodiment of the present disclosure.

With the development of internet technology, the development of web page development technology is rapidly developed, and development efficiency is greatly improved. Therefore, the functions carried by the web pages are more and more, and the volumes of large-scale web page items are expanding increasingly. In order to relieve the pressure caused by the overlarge volume of the project, the project is often split into a plurality of small functional modules, and the portal uniformly organizes the functional modules to form a complete project.

Here, the portal page generating method includes:

and acquiring a function module index file, converting the function module into a route instance for export, and providing the route instance for a portal website.

It should be noted that, in this embodiment, the index file of the functional module may be actually understood as the component path described in the foregoing embodiment. Obtaining a routing instance of a functional module by obtaining a component path of the functional module and obtaining the routing instance of the functional module through the component path, wherein the routing instance comprises: and the corresponding relation between the component path and the component identifier is exported.

And configuring a routing module of the portal webpage, scanning a function module catalog, and reading a routing instance to register to the global route.

Here, a global route is first configured for the portal page so that the portal page can be accessed according to the global route. And reading and registering the routing instance of the function module into the global route by scanning the function module catalog.

The portal page may be accessed by accessing the global route.

According to the method and the device, on the premise of not losing performance, the functional modules of the portal webpage are split, even the components are split, so that large projects are reasonably split, the functional modules or the components can be independently developed, the development efficiency is improved, and a developer only needs to pay attention to the functional modules of the developer, so that the development flow is simplified.

Further, portal pages and functional modules use the same software framework, and by configuring the packaging tool, the same dependent compilation can be skipped, so that the volume of the project is reduced. Meanwhile, due to the common dependence, after the portal webpage loads the common dependence, the functional module only needs to record fewer codes, and the loading speed is improved.

Further, because the portal page and the function modules use the same software framework, all the function modules can share the state of the portal page, the communication problem between the function modules and the portal page is solved, the update operation of the function modules based on the state is reduced, and the user experience is improved.

Fig. 8 is a block diagram of a portal page generating apparatus according to an exemplary embodiment. Referring to fig. 8, the apparatus includes a first acquisition module 81, a second acquisition module 82, a registration module 83, and a generation module 84;

a first obtaining module 81 configured to obtain a component path of a function module of the portal page;

a second obtaining module 82 configured to obtain a routing instance of the functional module based on the component path of the functional module, wherein the routing instance includes: a corresponding relationship of component paths and component identifications;

A registration module 83 configured to export and register the route instance into a global route configured for the portal page;

a generation module 84 is configured to generate the portal page by accessing the global route.

In an alternative embodiment, the generating module 84 further includes:

In an alternative embodiment, the acquisition sub-module is further configured to:

Or,

In an alternative embodiment, different of the components are deployed with the same software framework.

Fig. 9 is a block diagram of a portal page generating apparatus according to another exemplary embodiment. Referring to fig. 9, the apparatus includes:

a sending module 91, configured to send a routing instance of the functional module of the portal webpage and/or a component corresponding to the routing instance to a client, where the routing instance includes: and the routing instance and/or the component corresponding to the routing instance are used for the client to generate the portal webpage.

In an alternative embodiment, the apparatus further comprises:

a receiving module 92 configured to receive a first access request of the client for a global route of a portal page;

the sending module 91 is further configured to send a routing instance of the functional module of the portal page and/or a component corresponding to the routing instance to the client based on the first access request.

The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.

Fig. 10 is a block diagram of a client 1000, according to an example embodiment. For example, client 1000 may be a mobile phone, computer, digital broadcast client, messaging device, game console, tablet device, medical device, exercise device, personal digital assistant, or the like.

Referring to fig. 10, a client 1000 may include one or more of the following components: a processing component 1002, a memory 1004, a power component 1006, a multimedia component 1008, an audio component 1010, an input/output (I/O) interface 1012, a sensor component 1014, and a communication component 1016.

The processing component 1002 generally controls overall operation of the client 1000, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 1002 can include one or more processors 1020 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 1002 can include one or more modules that facilitate interaction between the processing component 1002 and other components. For example, the processing component 1002 can include a multimedia module to facilitate interaction between the multimedia component 1008 and the processing component 1002.

The memory 1004 is configured to store various types of data to support operations at the client 1000. Examples of such data include instructions for any application or method operating on client 1000, contact data, phonebook data, messages, pictures, video, and the like. The memory 1004 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

The power component 1006 provides power to the various components of the client 1000. Power component 1006 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for client 1000.

The multimedia component 1008 includes a screen between the client 1000 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia assembly 1008 includes a front-facing camera and/or a rear-facing camera. When the client 1000 is in an operation mode, such as a photographing mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

The audio component 1010 is configured to output and/or input audio signals. For example, the audio component 1010 includes a Microphone (MIC) configured to receive external audio signals when the client 1000 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in memory 1004 or transmitted via communication component 1016. In some embodiments, the audio component 1010 further comprises a speaker for outputting audio signals.

The I/O interface 1012 provides an interface between the processing assembly 1002 and peripheral interface modules, which may be a keyboard, click wheel, buttons, and the like. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.

The sensor assembly 1014 includes one or more sensors for providing status assessment of various aspects to the client 1000. For example, the sensor assembly 1014 may detect an on/off state of the client 1000, a relative positioning of the components, such as a display and keypad of the client 1000, the sensor assembly 1014 may also detect a change in position of the client 1000 or a component of the client 1000, the presence or absence of a user's contact with the client 1000, an orientation or acceleration/deceleration of the client 1000, and a change in temperature of the client 1000. The sensor assembly 1014 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. The sensor assembly 1014 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 1014 can also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 1016 is configured to facilitate communication between the client 1000 and other devices, either wired or wireless. The client 1000 may access a wireless network based on a communication standard, such as WiFi,2G or 3G, or a combination thereof. In one exemplary embodiment, the communication component 1016 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 1016 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, the client 1000 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the above method.

In an exemplary embodiment, a non-transitory computer readable storage medium is also provided, such as memory 1004, including instructions executable by processor 1020 of client 1000 to perform the above-described method. For example, the non-transitory computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

A non-transitory computer-readable storage medium, which when executed by a processor of a client, enables the client to perform the portal page generation method described in the above embodiments.

Fig. 11 is a block diagram illustrating a server 1100 according to an example embodiment. Referring to FIG. 11, server 1100 includes a processing component 1122 that further includes one or more processors and memory resources, represented by memory 1132, for storing instructions, such as application programs, executable by processing component 1122. The application programs stored in memory 1132 may include one or more modules each corresponding to a set of instructions. Further, processing component 1122 is configured to execute instructions to perform the portal page generation method described above.

The server 1100 may also include a power component 1126 configured to perform power management of the server 1100, a wired or wireless network interface 1150 configured to connect the server 1100 to a network, and an input-output (I/O) interface 1158. The server 1100 may operate based on an operating system stored in the memory 1132, such as Windows Server, mac OS XTM, unixTM, linuxTM, freeBSDTM, or the like.

Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the invention and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.

It is to be understood that the invention is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the invention is limited only by the appended claims.

Claims

1. The portal webpage generating method is characterized by being applied to a client and comprising the following steps:

acquiring a component path of a functional module of the portal webpage;

based on the component path of the functional module, obtaining a routing instance of the functional module from a server side, wherein the routing instance comprises: a corresponding relationship of component paths and component identifications;

Exporting and registering the route instance into a global route configured for the portal page; the global route comprises all component paths in the portal webpage and component identifiers corresponding to the component paths;

generating the portal page by accessing the global route;

wherein the generating the portal page by accessing the global route includes:

loading the function module within the portal page based on the component;

wherein, based on the component identifier, the obtaining the component corresponding to the component identifier includes:

2. The method of claim 1, wherein the obtaining the component corresponding to the component identifier based on the component identifier further comprises:

or,

and if the global route is not accessed for the first time and the functional module is accessed, acquiring the component corresponding to the component identifier on the local or the component platform based on the component identifier.

3. A method according to any one of claims 1 to 2, wherein different of said components are deployed with the same software framework.

4. The portal webpage generating method is characterized by being applied to a server and comprising the following steps:

and sending the routing instance of the functional module of the portal webpage to a client, wherein the routing instance comprises the following steps: the route instance is used for the client to export and register into a global route configured for the portal page, and the global route comprises all component paths in the portal page and component identifiers corresponding to the component paths; the global route is used for determining the component identifier of the routing instance of the function module of the portal webpage by the client, sending an acquisition request to a component platform according to the component identifier, receiving the component corresponding to the component identifier returned by the component platform based on the acquisition request, and loading the function module in the portal webpage based on the component.

5. The method according to claim 4, wherein the method further comprises:

the sending the routing instance of the functional module of the portal page to the client side includes:

and sending the routing instance of the functional module of the portal page to the client based on the first access request.

6. A portal page generating device, which is applied to a client, and comprises:

a second obtaining module, configured to obtain, from a server side, a routing instance of the functional module based on the component path of the functional module, where the routing instance includes: a corresponding relationship of component paths and component identifications;

the registration module is configured to export and register the route instance into a global route configured for the portal page, wherein the global route comprises all component paths in the portal page and component identifiers corresponding to the component paths;

a generation module configured to generate the portal page by accessing the global route;

Wherein, the generating module further includes:

a loading sub-module configured to load the functional module within the portal page based on the component;

the acquisition sub-module is further configured to:

7. The apparatus of claim 6, wherein the acquisition sub-module is further configured to:

or,

8. The apparatus of any of claims 6 to 7, wherein different of the components are deployed with the same software framework.

9. A portal page generating device, which is applied to a server, and comprises:

the sending module is configured to send the routing instance of the functional module of the portal webpage to the client, wherein the routing instance comprises: the route instance is used for the client to export and register into a global route configured for the portal page, and the global route comprises all component paths in the portal page and component identifiers corresponding to the component paths; the global route is used for determining the component identifier of the routing instance of the function module of the portal webpage by the client, sending an acquisition request to a component platform according to the component identifier, receiving the component corresponding to the component identifier returned by the component platform based on the acquisition request, and loading the function module in the portal webpage based on the component.

10. The apparatus of claim 9, wherein the apparatus further comprises:

the sending module is further configured to send a routing instance of the functional module of the portal page to the client based on the first access request.

11. A client, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

acquiring a component path of a functional module of a portal page;

generating the portal page by accessing the global route;

wherein the generating the portal page by accessing the global route includes:

loading the function module within the portal page based on the component;

12. A server, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

transmitting a routing instance of a functional module of a portal page to a client, wherein the routing instance comprises: the route instance is used for the client to register in a global route configured for the portal page, and the global route comprises all component paths in the portal page and component identifiers corresponding to the component paths; the global route is used for determining the component identifier of the routing instance of the function module of the portal webpage by the client, sending an acquisition request to a component platform according to the component identifier, receiving the component corresponding to the component identifier returned by the component platform based on the acquisition request, and loading the function module in the portal webpage based on the component.

13. A non-transitory computer readable storage medium having stored thereon a computer program, characterized in that the program is executed by a processor to implement the method steps of any of claims 1 to 3 or claims 4 to 5.