Client-side customization and rendering of web content
By analyzing and dynamically generating updated style sheets and content on the client device, the problem of high consumption of web page custom rendering resources in the existing technology is solved, and rich client device support and resource conservation are achieved.
Patent Information
- Application Number
- CN202010082085.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-02-08
- Filing Date
- 2020-02-07
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2040-02-22
AI Technical Summary
The prior art is difficult to dynamically customize the style, layout and format of web pages on client devices, and requires a large number of resources and multiple requests from the back-end server to support rendering of various client devices.
By analyzing web page contents on the browser executed on the client device, identifying element identifiers and characteristics, dynamically generating updated style sheets and contents, injecting them into the original content, realizing customized rendering of web pages, and reducing dependence on the back-end server .
It realizes rich customization of web page styles, layouts and formats, saves back-end processing resources and network resources, reduces multiple requests and responses, and supports more types of client device rendering.
Smart Images

Figure CN111552897B_ABST
Abstract
Description
Background Art
[0001] A web server provides content to a client device by transmitting HTTP (Hypertext Transfer Protocol) messages and / or various web-based protocols to provide web files to its various clients. The client device generally transmits a request through its web browser, and then receives a web page from the web server in the form of a markup language document (such as a Hypertext Markup Language (HTML) file, an Extensible Markup Language (XML) file) and associated web-based resources (such as JavaScript files, style sheets (e.g., CSS) and image files, video files, and other web content to be embedded in the web page). The web browser on the client device can then parse the markup language document received from the web server and render the web page content to the display of the client device. The web browser displays the elements by applying layout rules and using the specific rendering style of the elements defined by the style sheet.
[0002] As the number and types of client devices (including desktop computers, laptop computers, tablet computers, smart phones, smart watches, web-enabled TVs, etc.) continue to increase, it is important to render web content in different ways depending on the type and characteristics of the client device. For this reason, a web server generally creates multiple copies of a web page / web content to render on different client devices. When a client requests a web page, the server can identify the client device type and / or platform from the request header, and can retrieve and transmit a specific set of markup language files, style sheets, etc. In addition, some web content providers can support limited user customization of web pages, such as by providing a "dark mode" feature within a web page, which allows the user to switch the rendered web page between lighter and darker styles, or by allowing the client user to change the font size displayed within the web page. However, support for custom features is limited and must be implemented by a back-end web server. Summary of the invention
[0003] Thus, the embodiments described herein relate to techniques for generating and injecting updated style sheets and / or other web content via a web browser executed on a client device, thereby updating the style, layout and format of web content rendered on the client device, wherein little or no support required for changing the back-end web server is required. For example, some embodiments described herein include that the client device requests, receives and analyzes web content from a web server. The client device can analyze web content to identify each element within a web page, including element identifiers, values and / or other characteristics. The client device can transmit subsequent requests to the web server to retrieve element definitions, which can be specific element identifiers and / or element groups. Using element definitions, the client device can dynamically generate updated web files (e.g., markup language files, style sheets, etc.), and then inject the updated web files (e.g., using JavaScript) into the remaining web content received from the web server to be displayed on the client device. These technologies allow specific formats, layouts and styles to be applied to web elements (such as tables, images, controls and any other web elements) using updated style sheets and other web content dynamically generated by the client device.
[0004] In addition, according to some embodiments, a web browser executed on a client device may determine the form factor, user input controls, and / or various other client device capabilities and features, and may use the determined device features to generate updated presentation markup, style sheets, and the like for web content. Such customization may also be performed based on the characteristics of the current user operating the client device, for example, by changing element sizes, color schemes, user input controls, and the like based on the preferences or characteristics of the current user that may be determined by the client web browser. Additionally, in some embodiments, changes to the form factor and / or features of the client device may be detected after the initial web content is requested and rendered. For example, a smartphone or desktop client may be connected to a television or other external display (e.g., via screen mirroring or pairing), thereby allowing the display of the client smartphone or desktop to be projected to the external display. In such cases, the client device may regenerate markup and / or style sheets based on detection of a new external display (and / or any changes detected to the client device), thereby allowing the web content to be dynamically regenerated and rendered to the external display.
[0005] As discussed in detail below, the technology described herein provides advantages over conventional technologies for providing and tailoring web content to various client devices. For example, by analyzing and parsing web content, retrieving specific web element definitions, and then using dynamic code generation and injection performed by a browser executed on a client device to generate style sheets and other web resources, a large amount of back-end processing resources and network resources can be saved. In addition, by supporting robust client-specific customization of web content styles, layouts, formats, etc., fewer code changes (even no changes) can be required on the server side, thereby avoiding additional software development, testing, and deployment processing. Similarly, the web server can avoid the requirement of generating and updating multiple copies and versions of Cascading Style Sheets (CSS) for various client devices, but directly provides the web content and element definitions required for generating and injecting dynamic CSS for the client device at the client web browser. Finally, the embodiments described herein support layout, style, and format changes / customizations of many more types than can be supported using conventional technologies. The client device may have more information about its own specific platform, characteristics, capabilities, form factor than the web server, so the client can determine the optimal layout, style, and format for individual web elements and entire web pages based on these specific characteristics. BRIEF DESCRIPTION OF THE DRAWINGS
[0006] Figure 1 A client-server network environment including various server-side systems configured to provide web content to client devices according to one or more embodiments of the invention is illustrated.
[0007] Figure 2 is an example user interface of a customized web portal including a plurality of pagelet web elements according to one or more embodiments of the invention.
[0008] Figure 3 is a client-server flow diagram illustrating an example process for generating and rendering customized web content at a client device according to one or more embodiments of the invention.
[0009] Figure 4 is another flow chart illustrating an example process for generating and rendering web content having an updated style, format, and / or layout at a client device based on a client request in accordance with one or more embodiments of the invention.
[0010] Figure 5 A simplified client-server network environment is illustrated that includes a web server, a client device, and a second display associated with the client device in accordance with one or more embodiments of the invention.
[0011] Figure 6 is a diagram of a computer server and computing environment according to some embodiments of the present invention.
[0012] Figure 7 is a simplified block diagram depicting components of a cloud computing system and environment according to certain embodiments of the present invention.
[0013] Figure 8 is a schematic diagram of a computer system configured to perform techniques according to some embodiments of the invention.
[0014] In the drawings, similar components and / or features may have the same reference number. Additionally, various components of the same type may be distinguished by following the reference number with a dash and a second reference that distinguishes between the similar components. If only the first reference number is used in the specification, the description applies to any similar components having the same first reference number, regardless of the second reference number. DETAILED DESCRIPTION
[0015] In the following description, for the purpose of explanation, specific details are set forth in order to provide a thorough understanding of the various embodiments and examples. However, it is apparent that the various embodiments may be practiced without these specific details. For example, circuits, systems, algorithms, structures, techniques, networks, processes, and other components may be shown as components in block diagram form so as not to obscure the embodiments with unnecessary detail. The drawings and descriptions are not intended to be limiting.
[0016] Some examples, such as those disclosed with respect to the figures in this disclosure, may be described as processes, which are depicted as flowcharts, flow diagrams, data flow diagrams, structure diagrams, sequence diagrams, or block diagrams. Although a sequence diagram or flow diagram may describe an operation as a sequential process, many operations may be performed in parallel or simultaneously. In addition, the order of the operations may be rearranged. A process terminates when its operations are completed, but may have additional steps not included in the figure. A process may correspond to a method, function, procedure, subroutine, subprogram, etc. When a process corresponds to a function, its termination may correspond to the function returning to the calling function or main function.
[0017] The processing depicted herein may be implemented in software (e.g., code, instructions, programs), hardware, or a combination thereof, executed by one or more processing units (e.g., processor cores), such as the processing described with reference to the drawings in the present disclosure. The software may be stored in a memory (e.g., on a memory device, on a non-transitory computer-readable storage medium). In some examples, the processing depicted in the sequence diagrams and flow charts herein may be implemented by any system disclosed herein. The specific series of processing steps in the present disclosure are not intended to be limiting. Other step sequences may also be performed according to alternative examples. For example, alternative examples of the present disclosure may perform the steps outlined above in different orders. Moreover, the individual steps shown in the figure may include multiple sub-steps, which may be performed in various orders suitable for the individual steps. In addition, additional steps may be added or removed depending on the specific application. One of ordinary skill in the art will recognize many variations, modifications, and substitutions.
[0018] In some examples, each process in the figures of the present disclosure may be performed by one or more processing units. A processing unit may include one or more processors, including a single-core or multi-core processor, one or more cores of a processor, or a combination thereof. In some examples, a processing unit may include one or more special-purpose coprocessors, such as a graphics processor, a digital signal processor (DSP), etc. In some examples, some or all of the processing units may be implemented using customized circuits, such as an application-specific integrated circuit (ASIC) or a field programmable gate array (FPGA).
[0019] As described above, various aspects described herein relate to techniques (e.g., methods, systems, devices, computer-readable media storing computer-executable instructions for performing computing functions, etc.) for generating and injecting updated web content (e.g., style sheets, XML or HTML pages, etc.) using a web browser executed on a client device. Therefore, such techniques can support customization of styles, layouts, and formats of web pages, etc., specific to client devices, without requiring additional support or workload on back-end servers and networks. In some embodiments, a client device can request, receive, and analyze web content from a web server. Such web content can range from simple web pages to complex clients for interactive web-based portals and applications. A client device can analyze web content to identify various web elements within a web page, including element identifiers, values, and / or other characteristics. Using web element identifiers, a client device can request and obtain element definitions from a web server and / or other third-party servers. After receiving the web element definitions, the client device can dynamically generate updated web content files, including style sheets, markup language files, JavaScript files, etc., to implement specific styles or formats for each web element and / or implement specific layouts for a web page. For example, a JavaScript code injector may be used to inject updated web content files into the original web content received from a web server and then rendered to a client display via a client web browser. Thus, such techniques may allow automated client-specific customization and / or user-requested customization for specific formats, layouts, and styles to be applied to web elements (such as tables, images, controls, and any other web elements) without requiring additional requests and processing from web servers and other backend systems.
[0020] In addition, in some embodiments, a web browser executed on a client device can determine the form factor, user input controls, and / or various other client device capabilities and features, and can use the determined device features to generate updated presentation markup, style sheets, and the like for web content. Such customization can also be performed based on the characteristics of the current user operating the client device, for example, by changing element sizes, color schemes, user input controls, and the like based on preferences or features of the current user that can be determined by the client web browser. In addition, in some embodiments, changes to the form factor and / or features of the client device can be detected after the initial web content is requested and rendered. For example, a smartphone or desktop client can be connected to a television or other external display (e.g., via screen mirroring or pairing), thereby allowing the display of the client smartphone or desktop to be projected to the external display. In such cases, the client device can regenerate markup and / or style sheets based on detection of a new external display (and / or any changes detected to the client device), thereby allowing web content to be dynamically regenerated and rendered to the external display, again without requiring additional requests and processing from the web server and other backend systems.
[0021] Reference now Figure 1 , shows a network environment 100, which includes various server-side systems 140-160 configured to transmit web-based content to client devices 110 via one or more communication networks 130. As described in the following example, web pages and other web content can be generated by web servers 140 and / or back-end application servers 150 and provided to various client devices 110 by web servers 140. Web content can include markup language code files (e.g., HTML, XML, etc.), each of which can correspond to different web addresses / URLs and can define one or more web pages of a website or domain. Additional web content associated with and / or referenced by the markup language code files can include style sheets (e.g., Cascading Style Sheets (CSS)), image files, video files, and programmatic code files (e.g., script files, executable files). As shown in this example, web content files 161 (which can also be referred to as web resources) can be stored in one or more back-end data repositories 160, while other web content can be stored and / or generated by back-end application servers 150.
[0022] Various web elements can be represented in web content files 161, or generated by back-end server 150, including web elements embedded in markup language files and / or web elements representing data objects stored in separate web resource files 161. Such web elements can correspond to, for example, web page controls / components (such as frames, command buttons, headers, text blocks, titles, menu options, tables, paragraphs, and / or sentences). Additional web elements can include image files, video files, audio files, graphic files, etc., as well as more complex programmatic elements (such as small pages, applets, and other embedded executable files). As shown in this example, additional data can also be stored in server-side data repository 160, such as web element definition data 162 and client / user data 163.
[0023] The web element definition described in more detail below can refer to a collection of characteristics or features associated with any web content element 161. Therefore, the web element definition 162 can define the size or size range of the web element that should be rendered within the web page, and / or the style that should be used when rendering the web element on the web page. Certain types of web element definition data can be applied to all possible web elements, while other web element definition data can be specific to the type of web element. For example, a grid / table web element, the web element definition 162 can include data indicating whether to display the header, title and (one or more) navigation bar and where they should be rendered on the table object, whether the grid / table element includes embedded pop-up help, background style, characteristics of the row action button, column header style, display footer characteristics, etc. In addition, for any web object / element, the web element definition 162 can include whether it is permitted to suppress (and / or whether the web element should be suppressed) when the web element is displayed on a screen of various form factors (e.g., small, medium, large or extra-large form factors, etc.). In some embodiments, each web element definition in the data repository 160 can be stored with one or more associated element identifiers. Element identifiers within the data repository 160 may be unique to individual web elements (e.g., a specific frame, a specific table, a specific text box, etc.) and / or to specific types of web elements (e.g., all frames, all tables, all text boxes, etc.). Additionally, element identifiers may be used to define groups of web elements to which a common set of properties should be applied when rendered.
[0024] The client device 110 can send web requests and receive web content from the application server 150 and / or the web server 140 via the network 130. The network 130 may include, for example, the Internet, a local area network, and / or a wide area network, etc. Although only a single network 130 is shown in this example, the network 130 may include any number of different communication networks between any computer servers and devices described herein. Various embodiments of the communication network 130 may employ one or a combination of different types of networks, such as IP-based computer networks, telecommunication networks, cellular networks, short-range and long-range wireless networks, cable or satellite networks, and / or any combination of these networks and / or other networks. The client device 110 may include a mobile device such as a smart phone, a tablet computer, a virtual assistant device, a vehicle-based device, and a wearable computing device (e.g., a smart watch, smart glasses, etc.). Such a mobile device may run a variety of mobile operating systems and may enable the Internet, email, short message service (SMS), Bluetooth, etc. Mobile radio frequency identification (M-RFID) and / or other communication protocols. Other client devices 110 may be general-purpose personal computers or special-purpose computing devices, including, for example, personal computers, laptop computers, workstation computers, projection devices, and interactive room display systems. In addition, client devices 110 may be any other electronic device capable of communicating over network(s) 130, such as thin client computers, Internet-enabled gaming systems, business or home appliances, and / or personal messaging devices.
[0025] As shown in this example, the client device 110 may include multiple software applications 120, including one or more web browsers 122 and browser plug-ins 124 (also referred to as browser extensions). As discussed in more detail below, the code within the client web browser 122 and / or plug-in 124 may be configured to analyze various elements of web content received from a web server, retrieve corresponding web element definitions, and then dynamically generate updated cascading style sheets (CSS), markup language documents, and / or other web content at the client side 110, without minimal intervention (or no intervention) required by the server system 140-160. In addition, the browser extension and / or plug-in 124 may include functionality and support a user interface to allow an administrator user to manually request and implement updates to the style, format, and / or layout of web content rendered at the client device 110. The code within the browser 122 and / or plug-in 124 may also be configured to automatically detect various features and capabilities of the client device 110, and detect and respond to connections between the client device 110 and an associated client device or display 110, as discussed below. In addition, although several examples are described with reference to browser extensions or plug-ins 124, it should be understood that the techniques discussed herein are not limited to extensions or plug-ins. For example, any browser extension or plug-in functionality described herein may additionally or alternatively be implemented within the browser 122, or as a piece of code embedded on the server side into a native web page transmitted to the client 110. Therefore, in any of these examples (e.g., code within the browser 122, within the plug-in / extension 124, embedded within a web page, or located elsewhere on the client device 110), the code may continue to execute after the browser 122 has completed loading the web page at the client device 110.
[0026] Reference now Figure 2, showing an example user interface 200. In this example, the user interface 200 can be generated by a customized web portal application, which can tailor specific web elements and content for the current user of the web portal application. Therefore, unlike simple HTML pages or other static web content, the user interface 200 can be dynamically generated based on the current user, the privileges and authorizations of the user to access certain applications via the portal, and the user's preferences for components to be displayed, screen layout, etc. Therefore, in this example, multiple small page web parts 220 can be dynamically generated and displayed for a specific user, wherein each small page part 220 corresponds to a specific portal application or component currently accessible to the user. The menu 210 can include a common set of components that are displayed exactly the same for each user, but different functions can be performed when different users select the same menu button. Therefore, even when the menu 210 presented in the user interface has a similar or identical appearance, the underlying markup language code can also be different and / or a specific menu button can call different scripts / software functions.
[0027] In some embodiments, the web-based content served by web server 140 and rendered by client device 110 may be integrated with an end-user software product line (such as Oracle's The web page 200 may correspond to the fluid homepage or portal homepage of the interactive center of the portal 200 (eg, the homepage of the interactive center of the portal). In such a case, the web page 200 may be a homepage that aggregates relevant information and displays tiles 220 that provide access to the fluid application. In this example, the tiles 220 may be compared to the small pages in the classic portal, and they are navigation structures displayed on the fluid homepage 200. Like other small pages, the tiles 220 may be reusable user interface widgets. These tiles / widgets 220 may be designed to be displayed only in the portal 200, or may be designed to run on any webpage.
[0028] Web page 200 (which in some cases may be a fluid home page and in which components / tiles 220 are displayed) may share a common purpose or apply to a specific user or role (such as an employee role, an administrator role, a staff role, etc.) within a software application. A user may interact with tiles 220 on home page 200 and may select a specific tile to access the underlying application and perform routine tasks. Tiles 220 may typically have graphics on them depicting the purpose of the underlying application, which may help users identify tiles and associate tiles with applications. Some tiles 220 may also display current information, thereby providing a dashboard function for users to review high-level information for decision making or monitoring.
[0029] In some cases, when a user first visits the web page 200, the client web browser 122 can access the web server 140 and / or application server 150 to reload and refresh all content (e.g., tiles / widgets 220). The browser 122 can then manually re-render the home page 200 so that all real-time tiles 220 (and / or other web elements) display the most current representation of the underlying data. In addition, in some examples, individual tiles 220 and / or other web elements can be configured to refresh at a specific rate. Users can also be allowed to personalize their home page experience via the web page 200, for example, by creating or deleting personal home pages, adding and removing tiles 220 and / or other web elements from their home pages, and changing the title / features of their home pages.
[0030] In addition, certain web pages (including those provided by The page 200, such as a page displayed in a fluid user interface, may be designed to be displayed differently depending on the client device 110 accessing the user interface. For example, the same page 200 may be accessed via a desktop, laptop, tablet, or smartphone, and the layout of the page 200 may be different for each type of device. For example, on a tablet device, more fields may appear with more space between them, while on a smartphone device, fewer fields may appear and the display may adjust to the smaller space available on the smartphone.
[0031] Reference now Figure 3, shows an example of a flow chart, illustrating a process by which a client device and a web server collaborate to generate and render customized web content at a client device. As discussed in the following examples, the steps in these processes can be performed by the client device 110 and the web server 140 in collaboration with one or more additional server-side systems (e.g., 150-160). In other examples, some web content / web resources can be requested / retrieved from the web server 140, while other web content / web resources are retrieved directly from the application server 150, the data repository 160, or a third-party server operating separately. For example, substantial web content (e.g., web elements / resources themselves) can be requested and retrieved from one computer system 140-160, while style data (e.g., CSS), formatting, and / or layout data can be received from a separate computer system 140-160 or a third-party system. Multiple client devices can also collaborate similarly, for example, where a first client device 110a can request / receive web content, and then a second client device 110b can render and display the content. In addition, multiple different client devices 110 may share web elements in some cases, and / or may share web element style data, layout data, and / or format data. For example, a client device 110 may retrieve a collection of web resources from a web server 140, but may retrieve style data, etc. from a separate client device 110 or other local system. In addition, it should be understood that the processing described in these examples is not necessarily limited to Figure 1-Figure 2 and Figure 5 The computing systems, networks, and architectures shown in the drawings may also be implemented in other compatible computing systems and networks.
[0032] In step 301, the web client device 110 can generate a request for web content and transmit the request to the web server 140. In some cases, the request in step 301 can be a request for a specific web page / web resource corresponding to a universal resource locator (URL), similar to or identical to those used in conventional web page requests. The request in step 301 can also be a refresh request, initiated by a user or automatically initiated by a client-side browser 122 or other web application. The request in step 301 can also be a request within an ongoing web session and / or a user- or session-specific interaction with a web portal or web-based application. Therefore, the request in step 301 does not need to specify a new or unique URL, but can correspond to a call to a SOAP or REST web service, a JSON request, etc., which can convey parameters or other client-side interaction data to the web server 140 as part of an active session.
[0033] The transmission of the request 302 from the client device 110 to the web server 140 may be performed via TCP / IP, any known web-based protocol (e.g., HTTP / SOAP), and / or encryption. In some embodiments, the request 302 may include data identifying the current session, user, client device, client device characteristics, and / or platform. For example, certain header data within the request 302 or parameters embedded within the body of the request 302 and / or the request URL may include a session identifier, a user identifier, a client platform identifier, data identifying a client form factor, and / or the like.
[0034] In step 303, the server-side system including the web server 140 may receive and process the request, including retrieving and / or generating web-based content in response to the request 302. As described above, the responsive web-based content may include any number of static web resources, such as web page documents (e.g., HTML and XML files) and associated scripts (e.g., JavaScript files), style sheets (e.g., CSS files), embedded executable applications (e.g., applets), images, and other web-based resources, which may be retrieved from one or more data repositories 160. Additionally or alternatively, the request 302 may be a web service request, and the responsive web-based content in step 303 may include a response dynamically generated by one or more back-end web services executing within the application server 150, which may be supplemented by additional web elements / resources retrieved from the data repository 160. Thus, the response 304 transmitted back to the client device 110 may include active (e.g., programmatic) and / or passive web elements, and may be transmitted via a single message, a series of messages, a streaming session, etc. For example, response 304 may include one or more primary web page documents and a plurality of associated resources (eg, scripts, style sheets, images, executable applications, etc.) that may be used in rendering the primary web page and / or may be embedded within the primary web page.
[0035] In step 305, the client device 110 may analyze the web content received from the web server 140, parse the content to identify one or more individual web elements, and then determine a set of element identifiers (IDs) for the various web elements. In some embodiments, some or all of step 305 may be performed by native functions of the browser 122 and / or by a browser plug-in or extension 124. In some cases, the analysis and parsing in step 305 may be performed in response to an explicit client user request, while in other cases, step 305 may be automatically performed and may be transparent to the user of the client device 110. For example, certain implementations may be automatically performed based on client device data, user data, preferences, etc. to customize the received web page. In such implementations, step 305 may be automatically performed by the browser 122 and / or plug-in 124, and the web content 304 may not be rendered by the browser 122 on the client device 110 at all. However, in other implementations described below, the web content 304 received from the web server 140 may be initially rendered and displayed on the client device 110, after which the user may request to change the style, format, and / or layout of the content. In these embodiments, step 305 may or may not be initially performed upon receipt of web content 304, or alternatively may be performed in response to a user request for a style / format / layout change.
[0036] During the analysis of the received web content in step 305, the web content may be parsed to identify a plurality of web elements, and an identifier embedded in the web content may be retrieved for each identified web element. As described above, a web element may include any data object within the received web content 304 that has characteristics and / or identifiers that are different from other data objects within the web content 304. Thus, some web elements may be defined by tags within a markup language document (e.g., HTML or XML) of a web page, while other web elements may correspond to objects within a separate associated markup language document or an embedded image, script, or executable file. Thus, analyzing the web content in step 305 may include parsing a markup language document and / or other associated web content files (e.g., script files, image files, executable files, etc.) to identify and analyze specific data objects stored therein. For each web element encountered, the browser plug-in 124 (or other software code executing step 305) may retrieve one or more web element identifiers (or web element IDs) from the web content corresponding to the web element. A web element may be one or a combination of an object's name, an object's ID number, an object's type, an object's associated URL or address, and the like. For objects embedded in a markup language, the web element ID can be determined by parsing the markup language and analyzing its various tags, attributes, and sub-elements, and then determining the unique element identification data within the data object. For other types of web elements, the web element ID data can be determined by parsing a separate associated data object / file (including script files, image files, executable files, etc.) to determine the unique object identifier / characteristic associated with a specific web element. In some cases, the web element ID can be completely unique to the web element, while in other cases, the web element ID can only identify the type of the web element. For example, the browser plug-in 124 can identify a table object within the web content 304, and can assign a web element ID corresponding to its object type (such as "table" or "grid") to the table object. However, in another example, the browser plug-in 124 can identify a specific table based on its name / title characteristics, header, grid size, and / or content, and can assign a more specific web element ID to the table object, such as "Table 5692" or "Product Inventory Table Q1" or a corresponding alphanumeric code identifier unique to a specific table. Similar web element IDs can be determined for frames and framesets in web content, web page menus and headers, images, videos, text blocks, web controls, embedded widgets, and other active objects, etc.
[0037] In step 306, the client device 110 transmits the set of web element identifiers determined in step 305 back to the web server 140. In some cases, the transmission from the client device 110 to the web server 140 may include an alphanumeric list of web element identifiers found within the web content. Furthermore, in some embodiments, the transmission in step 306 may require multiple request-responses between the client device 110 and the server 140. For example, if duplicate web element IDs exist, multiple server trips (e.g., to transmit / compare additional features of the web elements) may be required to identify the correct web element identifier corresponding to the web element parsed from the web content by the browser 122 and / or the plug-in 124.
[0038] In addition, in some embodiments, when parsing web content, the browser 122 and / or plug-in 124 can determine and extract values associated with different web elements. For example, user interactive web elements (e.g., web controls) such as check boxes, radio buttons, text boxes, etc. can have associated values, such as checked / unchecked, selected / unselected, text / number entered in a text box, etc. Similarly, for web elements such as list boxes, grids, and tables, the browser 122 and / or plug-in 124 can capture table / list / grid identifiers and / or identifiers for each individual row, as well as the data within each row / cell. In step 306, it may not be necessary to transmit the data values of the various web elements to the web server 140, but these values can be stored locally on the client device instead.
[0039] As discussed below, potential advantages of the techniques discussed herein may include reducing or even eliminating multiple client-server requests and responses for updated web content. Because data can be extracted from web elements and stored on the client device 110 (e.g., in a browser memory), the client 110 does not need to retrieve web element data from the server 140 a second time when performing a client-side update to the format, style, or layout of the web content. Similarly, as discussed in more detail below, the client device 110 does not need to re-retrieve the HTML of the web content, CSS files, and other web content files (e.g., scripts, executable files, images, etc.) when performing a client-side update to the format, style, or layout of the web content. Instead, by parsing / transmitting the web element ID (steps 305-306) and then retrieving the corresponding web element definition (steps 307-308), the client web browser 122 and / or the plug-in 124 can regenerate the web content (e.g., CSS) on the client side using a client-side injected script, and then re-layout and re-render the web page.
[0040] As described above, in step 307, the web server may receive the client request 306 including the web element ID, may retrieve the corresponding web element definition from the data repository 160 and / or other data source, and then transmit the web element ID and the corresponding definition back to the client device 110 in step 308. The definition data for a particular web element may include data values / ranges of one or more features that define design metadata for the particular web element. Examples may include a number of pixels (or ranges) of an element, layout information, characteristics of an element, style data, etc. Such design metadata may be stored in a server-side system to allow a content provider and / or web server 140 to control (if desired) certain aspects of how a particular web element is displayed on a client device 110. As described above, the web element definition data 162 stored on the server side and transmitted to the client device 110 in step 308 may include style data, but such style data need not include a style sheet (e.g., a CSS file), but may include more compact style feature data (e.g., fonts, colors, style sets, spacing requirements, etc.). Indeed, as described above, not transmitting the complete CSS file but generating an updated CSS file at the client device 110 may have significant advantages with respect to server processing load, network load, and the like.
[0041] Thus, in step 309, the client device 110 may use the definition data for the web elements received in step 308 together with the web content previously received in step 304 to generate updated web content to be displayed on the client device 110. The generation of the updated web content in step 309 may include dynamically generating a new cascading style sheet (CSS file) to change the style of various web elements and / or the entire web page displayed via the browser 122. Additionally or alternatively, the browser 122 or plug-in 124 may regenerate some or all of the markup language files, scripts, and / or may make other modifications to any web content initially received in step 304.
[0042] In some embodiments, the dynamic generation and / or modification of web content in step 309 may be based on device specifications, user preferences, and / or based on explicit user requests received via a browser user interview. For example, the CSS and / or other web content generated in step 309 may be based on the specific hardware, software, and / or platform of the client device 110. In some cases, the browser plug-in 124 may determine client device characteristics, such as the display form factor of the client device 110 (e.g., the size, shape, quality / characteristics of the client display, etc.) and / or the input device features of the client device 110 (e.g., whether there is a touch screen, whether there is pen input, whether there is voice control, whether there is gesture recognition, etc.), and then use the combination of the client device characteristics and the web element definition data received in step 308 to determine the style / layout / format of the web element. For example, for a particular web element (e.g., a text box, button, image, etc.), the browser 122 / plug-in 124 code may use the pixel and style data for the element received in step 308 and the display form factor data of the client device 110 to determine the specific CSS style of the web element. In other examples, the style, format and / or layout of any element (and / or combination of elements) of the web content may be determined in step 309 based on the web element definition and locally determined client device 110 characteristics (e.g., display characteristics, input type, mobile device platform, etc.).
[0043] Finally, in step 310, the client device 110 (e.g., using the browser 122 and / or the plug-in 124) may update the web content received in step 304 based on any dynamically generated and / or modified CSS or other web content files in step 309, and then may render the updated / modified web content to the (one or more) displays of the client device 110. In some embodiments, the client device 110 may execute a code injection script to generate the CSS (or other web content) on the client side, and then inject (or integrate) the modified CSS (or other file) into the web content received in step 304. As described above, some client devices 110 may be associated with one display device, while other client devices 110 may be associated with multiple displays. The client display may be integrated (e.g., for tablet devices, smart phones, wearable devices, etc.), or may be a separate, separate display (e.g., for desktop computers, screen mirroring / pairing technologies, etc.).
[0044] In some embodiments, the web content received in step 304 may be initially rendered and displayed at the client device 110, and then the web content may be re-rendered and redisplayed in step 310. For example, the web browser 122 and / or the user interface itself executed on the client device 110 may support an on-the-fly style configuration feature that allows a user to dynamically change the style, layout, and / or format of a web page currently being displayed. For example, an embedded web control or browser feature within the user interface may be user-selectable and may allow a user to change the color scheme of the current web page (e.g., dark mode, light mode, or select a different color pattern), change the size of a web element on the page, change the text size or font, change text or element spacing, etc. These types of on-the-fly style configuration features may be accessed via a browser menu or via controls on the web page itself, and the style configuration changes may be applied to individual web elements, the entire web page, and / or the user's entire browsing session or future sessions. In these examples, the web browser 122 may perform a first rendering of the web page in steps 304-305, which may be visible to the user via a display screen, and then re-render the web page in steps 309-310, which may immediately and visibly change the appearance of the web page. Such changes may be initiated by an explicit user request, which may be received before step 305 in some embodiments or before step 309 in other embodiments. In addition, as described above, the re-rendering and appearance change of the web page need not require reloading of the web page and / or any additional request / response to the web server 140 or other server-side system.
[0045] In other embodiments, the steps in this example may be performed without two separate renderings / displays of web content. For example, instead of performing a first rendering of web content and then performing a second rendering that changes the current display (e.g., initiated by a user request), the steps in this example may be performed automatically so that the web content received in step 304 is rendered and displayed only once in step 310. For example, the request / receipt of web element definitions in steps 306-308 may be performed automatically by a web browser 122 or a plug-in 124. Additionally, the dynamic generation of CSS or other web content and the injection and integration of the new content received in step 304 into the web content may be performed automatically based on the characteristics of the client device 110, platform, or browser and / or based on previously defined user preferences or device preferences, etc. Therefore, these intermediate steps may be transparent to the user, and the first visible output from the web request in step 302 is the modified web content generated in step 310, including the injected code to modify the style, format, and / or layout. Moreover, as in the examples above, these examples also do not require reloading of the web page and / or any other request / response to the web server 140 or other server-side system.
[0046] Reference now Figure 4 , shows a flowchart illustrating the process of generating and rendering modified web content at a client device. Therefore, steps 401-405 in this example can be the same as those in the above Figure 3 The functions performed at the client device 110 during certain embodiments of the collaborative processing discussed in more detail. In particular, this example describes in more detail the steps performed via the client web browser 122 and / or browser extension 124 in allowing a user to change the style / format / layout of a web element, web page, and / or browsing session, immediately and without requiring additional content requests to be returned to the web server 140.
[0047] In step 401, the browser 122 receives and renders web content (e.g., web pages) on the applicable display(s) of the client device 110. The web content received and rendered in step 401 may include static web resources, such as web page documents (e.g., HTML and XML files) and associated scripts (e.g., JavaScript files), style sheets (e.g., CSS files), embedded executable applications (e.g., applets), images, and other web-based resources. These resources may be received from the web server 140 and / or other server-side systems and may be stored in the browser memory, where they may be analyzed, parsed, and then rendered into displayable web content, which may then be output to the client display.
[0048] In step 402, a request to change one or more aspects of the style, format, or layout of a currently displayed web page may be received from a user during a web browsing session. In some embodiments, a browser extension (e.g., plug-in 124) may provide an additional browser menu or menu option that may be selected by the user to select a change. Such a menu may be integrated within an existing browser menu, or may be added via a side menu, right-click menu option, etc. In some cases, a user control to change the style / format / layout of the current web page may be embedded in the rendered display of the web page itself.
[0049] As discussed above, various options may be provided to allow the user to change the style, layout or format of a web page. In some cases, the browser menu options may allow the user to change the color scheme of the current web page (e.g., dark mode, light mode, or select different color patterns), change the background pattern of the web page, change the size of the web elements on the page, change the text size or font, change the spacing between characters or elements, change the text style, change the size or display characteristics of the image on the page, change the layout of the web elements on the page, etc. It should be understood that a fixed or enumerated set of style / format / layout change options provided by the browser 122 or browser extension 124 is not required. On the contrary, additional potential advantages of these embodiments include: an unlimited number of possible style / format / layout changes and configurations can be supported on the client side using dynamically generated CSS (and / or other web content), and therefore no additional support or effort is required in the server-side system to pre-program CSS, or otherwise support a variety of possible style / format / layout options.
[0050] Therefore, in some embodiments, browser 122 or plug-in 124 can allow the user to make one or more instant changes to the currently displayed web page by dynamically generating CSS (and / or other web content) on the client side, without requesting additional web content from the server side. In some examples, the menu, change options and user interface provided by browser plug-in 124 can allow the user not only to change the current web page, but also can be applied to the rest of the user's web browsing session and / or be applied to the user's future web browsing session on client device 110. In addition, in some embodiments, the menu, change options and user interface provided by browser plug-in 124 can allow the user to change individual web elements instead of the entire page. For example, change the background of a frame without changing the background of other frames in the page, change the style of some web controls without changing the style of other web controls in the page, etc.
[0051] In step 403, the browser 122 and / or extension 124 executing on the client device 110 can dynamically regenerate the CSS to replace the original CSS received in step 401. In some cases, the browser extension 124 can only regenerate certain blocks of CSS content and inject them into the received CSS file, while in other cases, the browser extension 124 can regenerate and replace the entire CSS file. In addition, although this example only involves CSS files, as discussed above, the browser 122 and / or extension 124 can be configured to also regenerate and replace different types of web content, including markup language files, script files, image files, executable files, etc.
[0052] The regeneration of CSS (or other web content) can be performed based on the user change request and the user's selection of the new style / format / layout configuration of the web element and / or web page received in step 402. For example, if the user requests a different background, color scheme, font style, etc., the browser extension 124 can replace or modify the original CSS received in step 401 to achieve the desired change. In addition, in some cases, the web element definition of the web element displayed on the current web page can be used for the dynamic regeneration of CSS (or other web content). As discussed above, the definition of a specific web element and / or web element group can be stored in a server-side system (e.g., data repository 160). The web definition can correspond to the design metadata stored and managed by the server-side system, the content provider and / or the web server 140 to control or limit how certain aspects of the web element are displayed on the client device 110. Although the retrieval and use of the web element definition can be optional in some embodiments, when the web element definition from the server side is used, the client can retrieve them during step 403 or at any time before step 402. When used, web element definitions may provide guidance and / or restriction parameters to clients regarding dimensions (eg, pixel ranges), allowed style parameters, and / or the like of individual web elements and / or groups of web elements.
[0053] Additionally or alternatively, the regeneration of the CSS (or other web content) in step 403 may be performed based on certain characteristics of the client device 110. For example, as discussed above, the dynamically generated CSS (and / or other web content) may be based on the specific hardware, software, and / or platform of the client device 110. For example, during or prior to step 403, the browser extension 124 may determine client device characteristics, such as the display form factor of the client device 110 (e.g., the size, shape, quality / characteristics of the client display, etc.) and / or the input device features of the client device 110 (e.g., whether there is a touch screen, whether there is pen input, whether there is voice control, whether there is gesture recognition, etc.). The browser 122 and / or extension 124 may then use a combination of (a) client device characteristics, (b) web element definition data retrieved from the server side, and / or (c) a user request to change the style / format / layout of the web content received in step 402 to determine the updated style changes and then generate the corresponding CSS (and / or other web content).
[0054] In step 404, the client device 110 may inject the updated CSS (and / or other web content) dynamically generated in step 403 into the web content received in step 401. Then, in step 405, the client device 110 may render the updated web page content onto a client display, which will include the updated style / format / layout of the web page. Thus, steps 404-405 may be similar or identical to step 310 discussed above. In some embodiments, the browser extension 124 may include a code injection script that generates the CSS (or other web content) at the client device 110 and then injects and / or integrates the modified CSS (or other file) into the original web content received in step 401. In some cases, the browser extension 124 may only regenerate certain blocks of the CSS content and inject them into the received CSS file, while in other cases, the browser extension 124 may regenerate and replace the entire CSS file.
[0055] In addition, as indicated by the arrows in steps 405 and 402, a web browsing user can make multiple changes to the style / format / layout of a web page, each of which causes another dynamic CSS regeneration, injection, and rendering in steps 403-405. However, as described above, these subsequent web page style modifications can be performed with fewer or no requests returned to the web server 140 or any other server-side component. For example, in an embodiment using web element definitions, they can be initially retrieved from the web server 140 and then stored locally at the client device 110. Any number of subsequent web page style modifications can then be performed without any communication back to the web server 140 or other server-side system.
[0056] Reference now Figure 5 , another example of a client-server network environment including a web server 140, a first client device 110a, and a second display device 110b in communication with the first client device 110a is shown. Therefore, this example can represent one or more possible implementations of the network environment 100 discussed above. In this example, the client device 110a can correspond to a wireless mobile device such as a smart phone or a tablet computer. The client device 110a can request and receive web content from the web server 140 and / or other server-side systems, and can support the above reference Figure 1-Figure 4 Any or all of the functions discussed for rendering web content, requesting / receiving web element definitions, determining device characteristics, dynamically generating web content, and injecting and rendering updated web content to customize the style, format, and / or layout of web content for a particular user and / or client device 110a. Thus, as described in detail above, the client device 110a may include a web browser 122 and / or a browser plug-in 124 that is configured to customize the style / format / layout of web content displayed on the client display 110a based on a request from a device user, device configuration preferences, and / or form factor and other characteristics of the client device 110a. In addition, as discussed above, the client device 110a may dynamically generate and render new CSS and other web content to change the appearance of the displayed web element / page without reloading the web page or performing any additional request / response to the web server 140 or other server-side system.
[0057] In addition, as shown in this example, the first client device 110a can be connected to or communicate with the second client display 110b. The client display 110b can be, for example, a television, a computer monitor, a projection device, or any other display screen. The connection link between the client device 110a and the separate display 110b can be a wired or wireless connection, and both devices 110a-110b can support the function of the client device 110a transmitting its current screen display to the separate display device 110b for output on the display. Examples of screen mirroring technology and other similar communication technologies for transmitting the screen display from the client device 110a to the display 110b can include Miracast standards, Google Chromecast, AirPlay, etc. In some cases, the client device 110a can transmit its entire screen display, while in other cases, it can only transmit a single application window to the separate display device 110b. Furthermore, in some embodiments, the client device 110a and the separate display device 110b may display the exact same content simultaneously, while in other embodiments, the content may be displayed on the separate device 110b instead of on the first client device 110a.
[0058] Use something like Figure 5 In the client-server network environment shown, additional embodiments can support dynamic customization of web content by the first client device 110a so as to transmit and render the web content on the separate display device 110b. For example, the operation of the web browser application 122 and / or the browser plug-in 124 on the client device 110a can also be configured to detect or receive a notification that the display screen is mirrored or transmitted to the separate display device 110b. In some embodiments, the browser plug-in 124 can receive updates / notifications from other software applications or communication components on the phone to determine that the client device 110a is transmitting its screen display to another display 110b, and also retrieve the form factor and / or other device characteristics of the separate display 110b.
[0059] Then, in response to detecting that the client device 110a is screen mirroring or otherwise sharing its display, the client device 110a may initiate (automatically or based on user request) the dynamic generation of updated CSS or other web content based on the specific device features (form factor, display or graphics quality, touch screen or input components, etc.) of the target display device 110b. In such cases, dynamically generating the updated CSS (or other web content) and injecting the updated CSS into the web content may be similar or identical to the above steps 403-404. However, in these cases, the client device 110a may determine the style, format, and layout configuration of the client device 110a based on the device features of the separated display 110b rather than the device features of the client device 110a. For example, if the form factor of the display 110b is much larger and / or different in shape than the form factor of the display of the client device 110a, the dynamically generated CSS (or other web content) may be generated by the client device 110a specifically for the form factor of the target display 110b. Similarly, style, format, and layout preferences may differ for different displays regarding desired color schemes for output, desired sizes of web elements on a page, desired text size or font, desired text or element spacing, etc., and in each of these cases, the client device 110a may dynamically generate updated CSS (and / or other web content) based on the device characteristics and the desired output style / format / layout to be used for the target device 110b.
[0060] Therefore, in some cases, the client device 110a can dynamically generate and inject a single copy of the modified CSS (and / or web content) based on the characteristics of the target display 110b. However, in other cases, display sharing features, screen mirroring features, etc. operated on devices 110a-110b can allow web content to be displayed on the client device 110a and the separate display 110b at the same time. In these embodiments, the client browser 122 and / or plug-in 124 can be configured to generate and maintain two separate copies of renderable web content: a first copy to be output to the display of the client device 110a and a second copy to be output to the separate target display 110b. These two separate copies of web content do not need to use exactly the same style, layout or format for their web elements and web pages. Therefore, for example, the client device 110a can perform separate dynamic CSS generation processing, code injection processing, content re-rendering and output processing, etc. for each of two (or more) separate displays. Thus, based on two separate dynamic CSS generation processes performed by the client devices, even when exactly the same web page (or any other content) is displayed by client device 110a and mirrored to a separate display 110b, the style, layout, and formatting of the rendered page or individual elements therein may be different for different display devices 110a-110b.
[0061] Reference now Figure 6 , depicts a simplified diagram of a distributed system 600 in which various examples discussed above may be implemented. In the example shown, the distributed system 600 includes one or more client computing devices 602, 604, 606, 608 coupled to a server 612 via one or more communication networks 610. The client computing devices 602, 604, 606, 608 may be configured to run one or more applications.
[0062] In various embodiments, server 612 may be adapted to run one or more services or software applications that enable one or more operations associated with system 100. For example, a user may use client computing devices 602, 604, 606, 608 (e.g., corresponding to content author devices) to access one or more cloud-based services provided via replication system 600.
[0063] In some examples, the server 612 may also provide other services or software applications, and may include non-virtualized environments and virtualized environments. In some examples, these services may be provided to users of the client computing devices 602, 604, 606, 608 as web-based services or cloud services or under a software as a service (SaaS) model. Users operating the client computing devices 602, 604, 606, 608 may in turn interact with the server 612 using one or more client applications to use the services provided by these components.
[0064] exist Figure 6 In the configuration shown, the server 612 may include one or more components 618, 620, and 622 that implement the functions performed by the server 612. These components may include software components, hardware components, or a combination thereof that may be executed by one or more processors. It should be appreciated that a variety of different system configurations are possible that may differ from the example distributed system 600.
[0065] The client computing devices 602, 604, 606, 608 may include various types of computing systems, such as portable handheld devices, such as smartphones and tablets; general-purpose computers, such as personal computers and laptops; workstation computers; wearable devices, such as head-mounted displays; gaming systems, such as handheld gaming devices, gaming consoles, and Internet-enabled gaming devices; thin clients; various messaging devices; sensors and other sensing devices, etc. These computing devices may run various types and versions of software applications and operating systems (e.g., Microsoft Apple or UNIX-like operating systems, Linux or Linux-like operating systems (such as Google Chrome TM OS)), where the operating system includes various mobile operating systems (e.g., Microsoft Windows Windows Android TM , Palm ). The client device may be capable of executing a variety of different applications, such as various Internet-related applications, communication applications (e.g., email applications, short message service (SMS) applications), and may use various communication protocols. The client device may provide an interface that enables a user of the client device to interact with the client device. The client device may also output information to the user via this interface. Although Figure 6 Only four client computing devices are depicted, but any number of client computing devices may be supported.
[0066] The network(s) 610 in the distributed system 600 may be any type of network familiar to those skilled in the art, and may support data communications using any of a variety of available protocols, including, but not limited to, TCP / IP (Transmission Control Protocol / Internet Protocol), SNA (Systems Network Architecture), IPX (Internetwork Packet Exchange), AppleTalk, etc. Merely by way of example, the network(s) 610 may be a local area network (LAN), an Ethernet-based network, a token ring, a wide area network, the Internet, a virtual network, a virtual private network (VPN), an intranet, an extranet, a public switched telephone network (PSTN), an infrared network, a wireless network (e.g., in any of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 protocol suites, Bluetooth and / or any other wireless protocol operating under the network) and / or any combination of these networks and / or other networks.
[0067] The server 612 may be composed of one or more general-purpose computers, dedicated server computers (including, for example, PC (personal computer) servers, The server 612 may be composed of a server, a mid-range server, a mainframe computer, a rack-mounted server, etc.), a server farm, a server cluster, or any other suitable arrangement and / or combination. The server 612 may include one or more virtual machines running a virtual operating system, or other computing architectures involving virtualization, such as one or more flexible pools of logical storage devices that can be virtualized to maintain a virtual storage device of the server. In various examples, the server 612 may be suitable for running one or more services or software applications that perform the above operations.
[0068] Server 612 can run an operating system, including any of the operating systems discussed above and any commercially available server operating system. Server 612 can also run any of a variety of additional server applications and / or middle-tier applications, including HTTP (Hypertext Transfer Protocol) servers, FTP (File Transfer Protocol) servers, CGI (Common Gateway Interface) servers, Server, database server, etc. Examples of database servers include, but are not limited to, database servers commercially available from Oracle, Microsoft, Sybase, IBM (International Business Machines), etc.
[0069] In some implementations, server 612 may include one or more applications to analyze and integrate data feeds and / or event updates received from users of client computing devices 602, 604, 606, and 608. As examples, data feeds and / or event updates may include, but are not limited to, data received from one or more third-party information sources and continuous data streams. feed, Updates or real-time updates, which may include real-time events related to sensor data applications, financial tickers, network performance measurement tools (e.g., network monitoring and traffic management applications), clickstream analysis tools, automobile traffic monitoring, etc. Server 612 may also include one or more applications that display data feeds and / or real-time events via one or more display devices of client computing devices 602, 604, 606, and 608.
[0070] The distributed system 600 may also include one or more data repositories 614, 616. These data repositories may provide a mechanism for storing various types of information, such as the information described in the various examples discussed above. The data repositories 614, 616 may reside in a variety of locations. For example, a data repository used by the server 612 may be local to the server 612, or may be remote from the server 612 and communicate with the server 612 via a network-based connection or a dedicated connection. The data repositories 614, 616 may be of different types. In some examples, the data repository used by the server 612 may be a database, such as a relational database, such as Oracle Corporation (Oracle ) and other suppliers. One or more of these databases can be adapted to respond to SQL format commands to implement retrieval, update and storage of data to or from the database.
[0071] In some examples, the application may also use one or more of the data repositories 614, 616 to store application data. The data repositories used by the application may be of different types, such as, for example, a key-value storage repository, an object storage repository, or a general storage repository backed by a file system.
[0072] In some examples, the cloud environment may provide one or more services, such as those discussed above. Figure 7 , shows a simplified block diagram of one or more components of a system environment 700, in which these services and other services may be provided as cloud services. Figure 7 In the example shown, cloud infrastructure system 702 can provide one or more cloud services that can be requested by users using one or more client computing devices 704, 706, and 708. Cloud infrastructure system 702 may include one or more computers and / or servers, which may include the above-mentioned Figure 6 Those computers and / or servers described by server 612. Figure 7 The computers in cloud infrastructure system 702 may be organized as general purpose computers, dedicated server computers, server farms, server clusters, or any other suitable arrangement and / or combination.
[0073] The network(s) 710 can facilitate data exchange and communication between the clients 704, 706, 708 and the cloud infrastructure system 702. The network(s) 710 can include one or more networks. The networks can be of the same or different types. The network(s) 710 can support one or more communication protocols, including wired protocols and / or wireless protocols, for facilitating communication.
[0074] Figure 7 The example depicted in FIG. 7 is only one example of a cloud infrastructure system and is not intended to be limiting. It should be appreciated that in other examples, the cloud infrastructure system 702 may have more Figure 7 More or fewer components than those depicted may be included, two or more components may be combined, or there may be a different configuration or arrangement of components. Figure 7 Three client computing devices are depicted, but any number of client computing devices may be supported in other examples.
[0075] The term "cloud service" is generally used to refer to services that are made available to users on demand by a service provider's system (e.g., cloud infrastructure system 702) and via a communications network such as the Internet. Typically, in a public cloud environment, the servers and systems that make up the cloud service provider's system are different from the customer's own local servers and systems. The cloud service provider's system is managed by the cloud service provider. Customers can therefore take advantage of cloud services provided by a cloud service provider without having to purchase separate licenses, support, or hardware and software resources for the services. For example, a cloud service provider's system can host applications, and users can order and use the applications on an as-needed and self-service basis via the Internet, without having to purchase infrastructure resources for executing the applications. Cloud services are designed to provide easy, scalable access to applications, resources, and services. Several providers offer cloud services. For example, Oracle Corporation of Redwood Shores, California Provides several cloud services, such as middleware services, database services, Java cloud services, etc.
[0076] In various examples, cloud infrastructure system 702 can provide one or more cloud services using different models, such as software as a service (SaaS) model, platform as a service (PaaS) model, infrastructure as a service (IaaS) model, and other models including hybrid service models. Cloud infrastructure system 702 may include application suites, middleware, databases, and other resources that enable the provision of various cloud services.
[0077] The SaaS model enables applications or software to be delivered to customers as a service over a communication network such as the Internet, without the customer having to purchase hardware or software for the underlying application. For example, the SaaS model can be used to provide customers with access to on-demand applications hosted by a cloud infrastructure system 702. Examples of SaaS services provided include, but are not limited to, various services for human resource / capital management, customer relationship management (CRM), enterprise resource planning (ERP), supply chain management (SCM), enterprise performance management (EPM), analytical services, social applications, and other services.
[0078] The IaaS model is typically used to provide infrastructure resources (e.g., servers, storage devices, hardware, and networking resources) to customers as cloud services to provide elastic computing and storage capabilities. Oracle Corporation Provides various IaaS services.
[0079] The PaaS model is generally used to provide platform and environment resources as a service, which enables customers to develop, run and manage applications and services without having to purchase, build or maintain such resources. Examples of PaaS services provided include, but are not limited to, Oracle Java Cloud Service (JCS), Oracle Database Cloud Service (DBCS), Data Management Cloud Service, various application development solution services, and other services.
[0080] In some examples, resources in cloud infrastructure system 702 can be shared by multiple users and can be dynamically reallocated based on demand. In addition, resources can be allocated to users in different time zones. For example, cloud infrastructure system 702 can enable a first set of users in a first time zone to utilize resources of the cloud infrastructure system for a specified number of hours, and then reallocate the same resources to another set of users in a different time zone, thereby maximizing utilization of the resources.
[0081] The cloud infrastructure system 702 can provide cloud services via different deployment models. In a public cloud model, the cloud infrastructure system 702 can be owned by a third-party cloud service provider, and cloud services are provided to any general public customer, where the customer can be an individual or an enterprise. In certain other embodiments, under a private cloud model, the cloud infrastructure system 702 can be operated within an organization (e.g., within an enterprise organization) and provide services to customers within the organization. For example, customers can be various departments of an enterprise, such as a human resources department, a payroll department, etc., or even individuals within an enterprise. In certain other embodiments, under a community cloud model, the cloud infrastructure system 702 and the services provided can be shared by several organizations in a related community. Various other models can also be used, such as a mix of the models mentioned above.
[0082] The client computing devices 704, 706, 708 may be the same as those described above. Figure 6 The client computing devices 602 , 604 , 606 , 608 are devices similar to the devices described above. Figure 7 The client computing devices 704, 706, 708 can be configured to operate a client application, such as a web browser, a proprietary client application (e.g., Oracle Forms), or some other application that can be used by a user of the client computing device to interact with the cloud infrastructure system 702 to use the services provided by the cloud infrastructure system 702.
[0083] In various examples, the cloud infrastructure system 702 may also provide "big data" and related computing and analysis services. The term "big data" is generally used to refer to extremely large data sets that can be stored and manipulated by analysts and researchers to visualize large amounts of data, detect trends, and / or otherwise interact with the data. The analysis that the cloud infrastructure system 702 may perform may involve using, analyzing, and manipulating large data sets to detect and visualize various trends, behaviors, relationships, etc. within the data. Such analysis may be performed by one or more processors, possibly processing data in parallel, performing simulations using the data, and the like. The data used for such analysis may include structured data (e.g., data stored in a database or structured according to a structured model) and / or unstructured data (e.g., data blobs (binary large objects)).
[0084] As in Figure 7 As depicted in the embodiment of , cloud infrastructure system 702 may include infrastructure resources 730 for facilitating the provision of various cloud services offered by cloud infrastructure system 702. Infrastructure resources 730 may include, for example, processing resources, storage or memory resources, networking resources, and the like.
[0085] In some examples, in order to facilitate efficient provisioning of these resources for supporting various cloud services provided by the cloud infrastructure system 702 for different customers, the resources can be bundled into a collection of resources or a collection of resource modules (also referred to as a "pod"). Each resource module or pod may include a pre-integrated and optimized combination of one or more types of resources. In some examples, different pods may be pre-provisioned for different types of cloud services. For example, a first set of pods may be provisioned for a database service, and a second set of pods may be provisioned for a Java service, where the second set of pods may include a different combination of resources than the pods in the first set of pods. For some services, resources allocated for provisioning services may be shared between services.
[0086] The cloud infrastructure system 702 itself may internally use services 732 that are shared by different components of the cloud infrastructure system 702 and facilitate the service provisioning of the cloud infrastructure system 702. These internally shared services may include, but are not limited to, security and identity services, integration services, enterprise repository services, enterprise manager services, virus scanning and whitelisting services, high availability, backup and recovery services, services for enabling cloud support, email services, notification services, file transfer services, and the like.
[0087] In various examples, the cloud infrastructure system 702 may include multiple subsystems. These subsystems may be implemented in software, hardware, or a combination thereof. Figure 7 714, the subsystems may include a user interface subsystem 712 that enables users or customers of the cloud infrastructure system 702 to interact with the cloud infrastructure system 702. The user interface subsystem 712 may include a variety of different interfaces, such as a web interface 714, an online store interface 716 (where cloud services provided by the cloud infrastructure system 702 are advertised and available for purchase by consumers), and other interfaces 718. For example, a customer may use a client device to request (service request 734) one or more services provided by the cloud infrastructure system 702 using one or more of the interfaces 714, 716, 718. For example, a customer may access an online store, browse cloud services provided by the cloud infrastructure system 702, and subscribe to one or more services provided by the cloud infrastructure system 702 that the customer wishes to subscribe to. The service request may include information identifying the customer and one or more services that the customer wishes to subscribe to. For example, a customer may place a subscription order for a service such as discussed above. As part of the order, the customer may provide information identifying the amount of resources required by the customer and / or within what time frame, etc.
[0088] In some examples, such as Figure 7In the example depicted in , cloud infrastructure system 702 may include an order management subsystem (OMS) 720 configured to process new orders. As part of this processing, OMS 720 may be configured to: generate an account for a customer if not already done; receive billing and / or accounting information from the customer that will be used to bill the customer for providing the requested service to the customer; verify the customer information; upon verification, book the order for the customer; and orchestrate various workflows to prepare the order for provisioning, among other operations.
[0089] Once properly authenticated, the OMS 720 may call an order provisioning subsystem (OPS) 724, which is configured to provision resources for the order, including processing resources, memory resources, and networking resources. Provisioning may include allocating resources to an order, and configuring resources to facilitate the services requested by the customer order. The manner in which resources are provisioned for an order and the type of resources provisioned may depend on the type of cloud service that the customer has ordered. For example, according to a workflow, the OPS 724 may be configured to determine a specific cloud service requested and identify multiple pods that may have been pre-configured for that specific cloud service. The number of pods allocated for an order may depend on the size / quantity / level / scope of the requested service. For example, the number of pods to be allocated may be determined based on the number of users supported by the service, the duration of the service being requested, and the like. The allocated pods may then be customized for the specific requesting customer to provide the requested service.
[0090] Cloud infrastructure system 702 can send a response or notification 744 to the requesting client to indicate when the requested service is ready. In some cases, information (e.g., a link) can be sent to the client so that the client can begin to use and utilize the benefits of the requested service.
[0091] The cloud infrastructure system 702 can provide services to multiple customers. For each customer, the cloud infrastructure system 702 is responsible for managing information related to one or more subscription orders received from the customer, maintaining customer data related to the order, and providing the requested services to the customer. The cloud infrastructure system 702 can also collect usage statistics about the customer's use of the subscribed services. For example, statistics can be collected for the amount of storage used, the amount of data transferred, the number of users, and the amount of system up time and system down time. This usage information can be used to bill the customer. Billing can be performed, for example, on a monthly basis.
[0092] The cloud infrastructure system 702 can provide services to multiple customers in parallel. The cloud infrastructure system 702 can store information of these customers, including possible proprietary information. In some examples, the cloud infrastructure system 702 includes an identity management subsystem (IMS) 728, which is configured to manage customer-specific information and provide separation of managed information so that information related to one customer cannot be accessed by another customer. The IMS 728 can be configured to provide various security-related services, such as identity services (such as information access management, authentication and authorization services), services for managing customer identities and roles, and related capabilities, etc.
[0093] Reference now Figure 8 , shows an example of a computer system 800 that can be used to implement the various examples discussed above. In some examples, the computer system 800 can be used to implement any of the various servers and computer systems described above. Figure 8 As shown in , computer system 800 includes various subsystems, including a processing subsystem 804, which communicates with multiple other subsystems via a bus subsystem 802. These other subsystems may include a processing acceleration unit 806, an I / O subsystem 808, a storage subsystem 818, and a communication subsystem 824. The storage subsystem 818 may include a non-transitory computer-readable storage medium 822 and a system memory 810.
[0094] The bus subsystem 802 provides a mechanism for making the various components and subsystems of the computer system 800 communicate with each other as expected. Although the bus subsystem 802 is schematically shown as a single bus, the alternative example of the bus subsystem can utilize multiple buses. The bus subsystem 802 can be any type of bus structure in several types of bus structures, and the bus structure includes a memory bus or a memory controller, a peripheral bus, a network bus, and a local bus using any bus architecture in various bus architectures. For example, such architectures can include an industrial standard architecture (ISA) bus, a microchannel architecture (MCA) bus, an enhanced ISA (EISA) bus, a video electronics standard association (VESA) local bus, and a peripheral component interconnect (PCI) bus (the PCI bus can be implemented as a mezzanine bus manufactured according to the IEEE P1386.1 standard), etc. It can also utilize an architecture based on networking, such as a socket, a pipe, TCP / IP, wired or wireless, local, virtual, cellular, and other.
[0095] The processing subsystem 804 controls the operation of the computer system 800 and may include one or more processors, application specific integrated circuits (ASICs), or field programmable gate arrays (FPGAs). The processor may include a single-core or multi-core processor. The processing resources of the computer system 800 may be organized into one or more processing units 832, 834, etc. The processing unit may include one or more processors (including single-core or multi-core processors), one or more cores from the same or different processors, a combination of cores and processors, or other combinations of cores and processors. In some examples, the processing subsystem 804 may include one or more dedicated coprocessors, such as a graphics processor, a digital signal processor (DSP), etc. In some examples, some or all of the processing units of the processing subsystem 804 may be implemented using custom circuits, such as application specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs).
[0096] In some examples, the processing units in the processing subsystem 804 can execute instructions stored in the system memory 810 or stored on the computer-readable storage medium 822. In various examples, the processing units can execute various programs or code instructions, and can maintain multiple programs or processes that are executed simultaneously. At any given time, some or all of the program code to be executed can reside in the system memory 810 and / or on the computer-readable storage medium 822 (including possibly on one or more storage devices). Through appropriate programming, the processing subsystem 804 can provide the various functions described above. In the case where the computer system 800 is executing one or more virtual machines, one or more processing units can be assigned to each virtual machine.
[0097] In some examples, a processing acceleration unit 806 may be provided for performing customized processing or for offloading some of the processing performed by processing subsystem 804 , thereby speeding up the overall processing performed by computer system 800 .
[0098] The I / O subsystem 808 may include devices and mechanisms for inputting information to the computer system 800 and / or for outputting information from or via the computer system 800. In general, use of the term "input device" is intended to include all possible types of devices and mechanisms for inputting information to the computer system 800. User interface input devices may include, for example, keyboards, pointing devices such as a mouse or trackball, touch pads or touch screens incorporated into a display, scroll wheels, click wheels, dials, buttons, switches, keypads, audio input devices with voice command recognition systems, microphones, and other types of input devices. User interface input devices may also include software such as Microsoft Windows that enables a user to control and interact with input devices. Motion sensing and / or gesture recognition devices, Microsoft 360 game controllers, devices that provide an interface for receiving input using gestures and spoken commands. User interface input devices may also include eye gesture recognition devices, such as detecting eye activity from a user (e.g., a "wink" when taking a picture and / or making a menu selection) and translating eye gestures into input devices (e.g., Google ) Blink detector. In addition, the user interface input device may include a user to enable the user to communicate with the voice recognition system (e.g., Navigator) for interacting with a voice recognition sensing device.
[0099] Other examples of user interface input devices include, but are not limited to, three-dimensional (3D) mice, joysticks or indicator rods, game pads and graphic tablets, and audio / video devices such as speakers, digital cameras, digital camcorders, portable media players, webcams, image scanners, fingerprint scanners, barcode readers 3D scanners, 3D printers, laser rangefinders, and eye tracking devices. In addition, user interface input devices may include, for example, medical imaging input devices such as computed tomography, magnetic resonance imaging, position emission tomography, medical ultrasound equipment. User interface input devices may also include, for example, audio input devices such as MIDI keyboards, digital musical instruments, etc.
[0100] In general, the use of the term "output device" is intended to include all possible types of devices and mechanisms for outputting information from the computer system 800 to a user or other computers. User interface output devices may include display subsystems, indicator lights, or non-visual displays such as audio output devices, etc. The display subsystem may be a cathode ray tube (CRT), a flat panel device such as one utilizing a liquid crystal display (LCD) or plasma display, a projection device, a touch screen, etc. For example, user interface output devices may include, but are not limited to, various display devices that visually convey text, graphics, and audio / video information, such as monitors, printers, speakers, headphones, car navigation systems, plotters, voice output devices, and modems.
[0101] The storage subsystem 818 provides a repository or data repository for storing information used by the computer system 800. The storage subsystem 818 provides a tangible, non-transitory computer-readable storage medium for storing basic programming and data constructs that provide some of the example functionality. Software (e.g., programs, code modules, instructions) that provide the above functionality when executed by the processing subsystem 804 can be stored in the storage subsystem 818. The software can be executed by one or more processing units of the processing subsystem 804. The storage subsystem 818 can also provide a repository for storing data used in accordance with the present disclosure.
[0102] The storage subsystem 818 may include one or more non-transitory memory devices, including volatile and non-volatile memory devices. Figure 8 As shown in , the storage subsystem 818 includes a system memory 810 and a computer-readable storage medium 822. The system memory 810 may include multiple memories, including a volatile main random access memory (RAM) for storing instructions and data during program execution and a non-volatile read-only memory (ROM) or flash memory in which fixed instructions are stored. In some embodiments, a basic input / output system (BIOS) may typically be stored in ROM, which contains basic routines that help to transfer information between elements within the computer system 800, such as during startup. RAM typically contains data and / or program modules currently operated and executed by the processing subsystem 804. In some embodiments, the system memory 810 may include multiple different types of memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), etc.
[0103] By way of example and not limitation, Figure 8 As shown in FIG. 8 , system memory 810 may load application programs 812 being executed, which may include client applications, web browsers, middle-tier applications, relational database management systems (RDBMS), etc., program data 811, and operating system 816. As an example, operating system 816 may include various versions of Microsoft Apple and / or Linux operating systems, various commercially available or UNIX-like operating systems (including but not limited to various GNU / Linux operating systems, Google OS, etc.) and / or mobile operating systems such as iOS, Phone, OS, 10OS and OS operating system.
[0104] Computer-readable storage media 822 may store programs and data structures that provide some example functions. Computer-readable media 822 may provide storage for computer-readable instructions, data structures, program modules, and other data for computer system 800. Software (programs, code modules, instructions) that provide the above functions when executed by processing subsystem 804 may be stored in storage subsystem 818. As an example, computer-readable storage media 822 may include non-volatile memory, such as a hard drive, a disk drive, a hard drive such as a CD ROM, a DVD, a Blu-ray, or a DVD-ROM. ) disk or other optical media. Computer readable storage media 822 may include, but are not limited to, The computer readable storage medium 822 may include a solid-state drive (SSD) based on non-volatile memory (such as a flash memory-based SSD, an enterprise flash drive, a solid-state ROM, etc.), a volatile memory-based SSD (such as a solid-state RAM, dynamic RAM, static RAM, DRAM-based SSD, a magnetoresistive RAM (MRAM) SSD), and a hybrid SSD using a combination of DRAM-based and flash memory-based SSDs. The computer readable storage medium 822 may provide storage for computer readable instructions, data structures, program modules, and other data for the computer system 800.
[0105] In some examples, storage subsystem 818 may also include a computer-readable storage medium reader 820, which may also be connected to computer-readable storage medium 822. Reader 820 may receive and be configured to read data from a memory device such as a disk, flash drive, or the like.
[0106] In some examples, computer system 800 can support virtualization technology, including but not limited to virtualization of processing and memory resources. For example, computer system 800 can provide support for executing one or more virtual machines. Computer system 800 can execute programs, such as management programs that facilitate the management and configuration of virtual machines. Each virtual machine generally runs independently of other virtual machines. Memory, computing (e.g., processor, core), I / O and networking resources can be allocated to the virtual machine. Each virtual machine usually runs its own operating system, which can be the same or different from the operating system executed by other virtual machines executed by computer system 800. Thus, multiple operating systems can be potentially run simultaneously by computer system 800.
[0107] The communication subsystem 824 provides an interface to other computer systems and networks. The communication subsystem 824 serves as an interface for receiving data from the computer system 800 and transmitting data from the computer system 800 to other systems. For example, the communication subsystem 824 can enable the computer system 800 to establish a communication channel to one or more client computing devices via the Internet for receiving information from the client computing devices and sending information to the client computing devices.
[0108] The communication subsystem 824 can support both wired and / or wireless communication protocols. For example, in some examples, the communication subsystem 824 may include a radio frequency (RF) transceiver component, a global positioning system (GPS) receiver component, and / or other components for accessing a wireless voice and / or data network (e.g., using cellular phone technology, advanced data network technology (such as 3G, 4G or EDGE (Enhanced Data Rates for Global Evolution)), WiFi (IEEE 802.11 family of standards), or other mobile communication technologies, or any combination thereof). In some examples, the communication subsystem 824 may provide a wired network connection (e.g., Ethernet) as an addition or alternative to a wireless interface.
[0109] The communication subsystem 824 can receive and transmit data in various forms. For example, in some examples, the communication subsystem 824 can receive incoming communications in the form of structured and / or unstructured data feeds 826, event streams 828, event updates 830, etc. For example, the communication subsystem 824 can be configured to receive (or send) data feeds 826 in real time from users of social media networks and / or other communication services, such as feed, Updates, web feeds (such as Rich Site Summary (RSS) feeds), and / or real-time updates from one or more third-party information sources.
[0110] In some examples, the communication subsystem 824 can be configured to receive data that may be continuous or unbounded in nature without a clear end in the form of a continuous data stream, where the continuous data stream can include an event stream 828 of real-time events and / or event updates 830. Examples of applications that generate continuous data can include, for example, sensor data applications, financial quote machines, network performance measurement tools (e.g., network monitoring and traffic management applications), clickstream analysis tools, automobile traffic monitoring, etc.
[0111] The communication subsystem 824 may also be configured to output structured and / or unstructured data feeds 826 , event streams 828 , event updates 830 , etc. to one or more databases that may be in communication with one or more streaming data source computers coupled to the computer system 800 .
[0112] Computer system 800 may be one of various types, including a handheld portable device (e.g., Cellular phone, computing tablets, PDAs), wearable devices (e.g., Google head mounted display), personal computer, workstation, mainframe, kiosk, server rack, or any other data processing system.
[0113] Due to the ever-changing nature of computers and networks, Figure 8 The description of the computer system 800 depicted in FIG. 8 is intended to be a specific example only. Figure 8 Many other configurations of more or fewer components of the system depicted are possible. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will understand other ways and / or methods to implement the various examples.
[0114] Although specific embodiments have been described, various modifications, changes, alternative constructions, and equivalents are possible. The embodiments described in this disclosure are not limited to operations within certain specific data processing environments, but can be freely operated within multiple data processing environments. In addition, although embodiments have been described using a series of specific transactions and steps, it is obvious to those skilled in the art that this is not intended to be limiting. Although some flow charts describe operations as sequential processing, many operations can be performed in parallel or simultaneously. In addition, the order of operations can be rearranged. The processing may have additional steps not included in the accompanying drawings. The various features and aspects of the above-mentioned embodiments can be used alone or in combination.
[0115] In addition, although the embodiments described in this disclosure have been described using a specific combination of hardware and software, it should be appreciated that other combinations of hardware and software are also possible. Some embodiments described herein can be implemented using only hardware or only software or a combination thereof. The various processes described herein can be implemented on the same processor or different processors in any combination.
[0116] Where a device, system, component or module is described as being configured to perform certain operations or functions, such configuration may be achieved, for example, by designing electronic circuits to perform the operations, by programming programmable electronic circuits (such as microprocessors) to perform the operations (such as by executing computer instructions or code, or a processor or core is programmed to execute code or instructions stored on a non-transitory storage medium), or any combination thereof. Processes may communicate using a variety of techniques, including but not limited to conventional techniques for inter-process communication, and different paired processes may use different techniques, or the same paired process may use different techniques at different times.
[0117] Specific details are given in this disclosure to provide a thorough understanding of the embodiments. However, embodiments may be practiced without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques have been shown without unnecessary details to avoid obscuring the embodiments. This description provides only example embodiments and is not intended to limit the scope, applicability, or configuration of other embodiments. On the contrary, the previous description of the embodiments will provide an enabling description for implementing various embodiments for those skilled in the art. Various changes may be made to the functions and arrangements of the elements.
[0118] Thus, the description and drawings should be regarded as illustrative rather than restrictive. However, it will be apparent that additions, subtractions, deletions and other modifications and changes may be made thereto without departing from the broader spirit and scope of the present disclosure. Thus, although specific embodiments have been described, these are not intended to be limiting; various modifications and equivalents are within the scope of the present disclosure.
Claims
1. A method for rendering web content on a client device, comprising: transmitting, by a client device executing a web browser, a first request to a web server, the first request identifying web content; Receiving, by a client device from a web server, one or more web-based resources for rendering web content requested by the client device, wherein the one or more web-based resources include a first markup language document specifying a first visual representation of the web content; analyzing, by the client device, the one or more web-based resources to identify one or more web elements within the web content; determining, by the client device, an element identifier for each of the one or more web elements based on analysis of the one or more web-based resources; transmitting, by the client device to the web server, a second request including an element identifier determined for each of the one or more web elements; In response to the second request, receiving, by the client device, a web element definition for each of the one or more web elements, wherein the web element definition specifies a range of dimension values for the web element; For each of the one or more web elements: Determining, by the client device, a dimension value within a range specified in a web element definition for the web element, wherein the value is determined by the client device based on device characteristics corresponding to the client device; and generating, by the client device, a modified web element corresponding to the web element, the modified web element having a size corresponding to the determined size value; generating, by the client device, a second markup language document specifying a second visual representation of the web content, wherein the second markup language document includes one or more modified web elements; replacing the first markup language document with the second markup language document; as well as The web content is rendered by the client device to a display of the client device using at least the second markup language document.
2. The method for rendering web content on a client device as claimed in claim 1, wherein generating the second markup language document by the client device comprises: An updated cascading style sheet (CSS) is generated, wherein the updated cascading style sheet is based on (i) one or more cascading style sheets previously received from the web server in response to the first request, and (ii) one or more web element definitions received from the web server in response to the second request.
3. A method for rendering web content on a client device as described in claim 1, wherein a first web element within the web content is a table including a first number of rows and a second number of columns, and wherein the received web element definition for the first web element identifies at least one of: an updated number of rows that is different from the first number, or an updated number of columns that is different from the second number.
4. The method of rendering web content on a client device of claim 1, wherein receiving a web element definition for each of the one or more web elements in response to the second request comprises: A first web element definition is received for the first web element defining at least one of a pixel requirement or a style requirement for the first web element.
5. The method of rendering web content on a client device as claimed in claim 1, further comprising: determining, by a web browser executing on the client device, a form factor of a display of the client device, Wherein the second markup language document is based on the determined form factor of the display of the client device.
6. The method of rendering web content on a client device as claimed in claim 5, further comprising, after rendering the web content to a display of the client device: detecting, by the client device, that a connection has been established between the client device and the second display; determining, by a web browser executing on the client device, a second form factor of a second display connected to the client device; generating, by the client device, a third markup language document specifying a third visual representation of the web content, wherein the generating of the third markup language document is performed based on a second form factor of a second display connected to the client device; as well as The web content is rendered by the client device using the third markup language document to a second display connected to the client device.
7. The method of rendering web content on a client device as claimed in claim 5, further comprising: determining, by a web browser executing on the client device, one or more functional device capabilities of the client device; The second markup language document is generated based on the determined functional device capabilities of the client device.
8. The method of rendering web content on a client device of claim 1, wherein analyzing the web content received from the web server in response to the first request comprises: For each particular web element of a plurality of web elements within the web content, determine: (i) an element identifier, (ii) a pixel value associated with the particular web element, and (iii) one or more properties of the particular web element, and (iv) one or more style values associated with the particular web element.
9. A client computing device comprising: One or more network interfaces configured to access a wide area network (WAN); one or more integrated or associated display devices configured to output graphical content; a processing unit, comprising one or more processors; A memory storing a set of computer-readable instructions that, when executed by the one or more processors, cause the client computing device to perform the following operations: transmitting, via a web browser executing on a client computing device, a first request to a web server, the first request identifying web content; receiving, from a web server, one or more web-based resources for rendering web content requested by a client computing device, wherein the one or more web-based resources include a first markup language document specifying a first visual representation of the web content; analyzing the one or more web-based resources to identify one or more web elements within the web content; determining an element identifier for each of the one or more web elements based on the analysis of the one or more web-based resources; transmitting a second request to a web server, the second request including an element identifier determined for each of the one or more web elements; In response to the second request, receiving a web element definition for each of the one or more web elements, wherein the web element definition specifies a range of dimension values for the web element; For each of the one or more web elements: determining a size value within a range specified in a web element definition for the web element, wherein the value is determined by the client computing device based on device characteristics corresponding to the client computing device; and generating a modified web element corresponding to the web element, the modified web element having a size corresponding to the determined size value; generating a second markup language document specifying a second visual representation of the web content, wherein the second markup language document includes one or more modified web elements; replacing the first markup language document with the second markup language document; as well as The web content is rendered using at least the second markup language document to one or more display devices integrated with or associated with the client computing device.
10. The client computing device of claim 9, wherein generating the second markup language document comprises: An updated cascading style sheet (CSS) is generated, wherein the updated cascading style sheet is based on (i) one or more cascading style sheets previously received from the web server in response to the first request, and (ii) one or more web element definitions received from the web server in response to the second request.
11. The client computing device of claim 9, wherein the first web element within the web content is a table comprising a first number of rows and a second number of columns, and wherein the received web element definition for the first web element identifies at least one of: an updated number of rows that is different from the first number, or an updated number of columns that is different from the second number.
12. The client computing device of claim 9, wherein receiving a web element definition for each of the one or more web elements in response to the second request comprises: A first web element definition is received for the first web element defining at least one of a pixel requirement or a style requirement for the first web element.
13. The client computing device of claim 9, the memory storing additional computer readable instructions that, when executed by the one or more processors, further cause the client computing device to: determining, by a web browser executing on the client computing device, a form factor of a first display device integrated with or associated with the client computing device, The second markup language document is based on the determined form factor of the first display device.
14. The client computing device of claim 13, the memory storing additional computer readable instructions that, when executed by the one or more processors, further cause the client computing device to: After rendering the web content, detecting that a connection has been established between the client computing device and the second display device; determining, by a web browser executing on the client computing device, a second form factor of a second display device connected to the client computing device; generating a third markup language document specifying a third visual representation of the web content, wherein the generating of the third markup language document is performed based on a second form factor of a second display device connected to the client computing device; as well as The web content is rendered to a second display device connected to the client computing device using a third markup language document.
15. The client computing device of claim 13, the memory storing additional computer readable instructions that, when executed by the one or more processors, further cause the client computing device to: determining, by a web browser executing on the client computing device, one or more functional device capabilities of the client computing device; Wherein the second markup language document is generated based on the determined functional device capabilities of the client computing device.
16. The client computing device of claim 9, wherein analyzing the web content received from the web server in response to the first request comprises: For each particular web element of a plurality of web elements within the web content, determine: (i) an element identifier, (ii) a pixel value associated with the particular web element, and (iii) one or more properties of the particular web element, and (iv) one or more style values associated with the particular web element.
17. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a client computing device, cause the one or more processors to render web content on the client computing device, the instructions comprising: transmitting, via a web browser executing on a client computing device, a first request to a web server, the first request identifying web content; receiving, from a web server, one or more web-based resources for rendering web content requested by a client computing device, wherein the one or more web-based resources include a first markup language document specifying a first visual representation of the web content; analyzing the one or more web-based resources to identify one or more web elements within the web content; determining an element identifier for each of the one or more web elements based on the analysis of the one or more web-based resources; transmitting a second request to a web server, the second request including an element identifier determined for each of the one or more web elements; In response to the second request, receiving a web element definition for each of the one or more web elements, wherein the web element definition specifies a range of dimension values for the web element; For each of the one or more web elements: determining a size value within a range specified in a web element definition for the web element, wherein the value is determined by the client computing device based on device characteristics corresponding to the client computing device; and generating a modified web element corresponding to the web element, the modified web element having a size corresponding to the determined size value; generating a second markup language document specifying a second visual representation of the web content, wherein the second markup language document includes one or more modified web elements; replacing the first markup language document with the second markup language document; as well as The web content is rendered to a first display device integrated with or associated with the client computing device using at least the second markup language document.
18. The non-transitory computer readable medium of claim 17, the instructions further comprising: determining, by a web browser executing on the client computing device, a form factor of a first display device integrated with or associated with the client computing device, The second markup language document is based on the determined form factor of the first display device.
19. The non-transitory computer readable medium of claim 18, the instructions further comprising: After rendering the web content, detecting that a connection has been established between the client computing device and the second display device; determining, by a web browser executing on the client computing device, a second form factor of a second display device connected to the client computing device; generating a third markup language document specifying a third visual representation of the web content, wherein the generating of the third markup language document is performed based on a second form factor of a second display device connected to the client computing device; as well as The web content is rendered to a second display device connected to the client computing device using a third markup language document.
20. The non-transitory computer readable medium of claim 18, the instructions further comprising: determining, by a web browser executing on the client computing device, one or more functional device capabilities of the client computing device; Wherein the second markup language document is generated based on the determined functional device capabilities of the client computing device.
Citation Information
Patent Citations
Methods for server-side recording of client browser state via markup language
CN102272757A
Dynamic generation of cascading style sheets
US20070220480A1
Stylesheet conversion engine
US20090300483A1
Web Page Variation
US20150317405A1
Progressively loading network content
US8682964B1
