Methods and systems for dynamically generating and reusing dynamic web content

• US 10,084,847 B1
• Filed: 12/20/2017
• Issued: 09/25/2018
• Est. Priority Date: 09/15/2011
• Status: Active Grant

• Current Assignee: Citicorp Credit Services Incorporated (Citigroup Incorporated)
• Original Assignee: Citicorp Credit Services Incorporated (Citigroup Incorporated)
• Inventors: Law-How-Hung, France, Ram, Ramadurai V.
• Primary Examiner(s): Recek, Jason D
• Application Number:
  US15/848,849
• Time in Patent Office: 279 Days
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: G06F 8/38 for implementing user interfaces
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

Methods and systems for generating and reusing dynamic web content involve, for example, automatically generating client-side code on a server at run time, and automatically downloading the client-side code to the client side at run time. The client-side code is executed on the client side to become a widget with dynamic behavior attributes displayed as a component of a web page on a display screen of a client-side computing device. Dynamic behavior of the client-side code may triggered via an event handler mechanism wherein properties of the client-side code are dynamically changed without affecting any other content on the web page. The widget may be redisplayed on a subsequent occasion with a change in the widget without regenerating the client-side code.

Claims

1. A system, comprising:

a client-side computing device having a processor coupled to memory and programmed to;

execute client-side code for content of a web page embedded with at least one tag to become a widget with dynamic behavior attributes as a component of the web page on a display screen of the client-side computing device;

trigger dynamic behavior of the client-side code for the content of the web page embedded with the at least one tag via the dynamic behavior attributes of the widget by an occurrence of an event based at least in part on a user interaction with the client-side computing device processor;

cache, on a server-side processor communicably coupled to the client-side computing device processor, the client-side code for the content of the web page embedded with the at least one tag according to a tag parameter when a change is implemented in the widget by said occurrence of the event; and

redisplay the widget on the display screen of the client-side computing device with the change implemented in the widget as the component of the web page on a subsequent occasion without regenerating the client-side code.

2. The system of claim 1, said client-side computing device processor being further programmed to cache, on the client-side processor, the client-side code for the content of the web page embedded with the at least one tag according to the tag parameter when no change is implemented in the widget by said occurrence of the event at the client-side processor.

3. The system of claim 1, the server-side processor being programmed to automatically generate and download, to the client-side computing device processor, the client-side code for content of the web page embedded with the at least one tag with dynamic behavior attributes for the widget within the client-side code for the content of the web page at run time.

4. The system of claim 3, the server-side processor being further programmed to provide the at least one tag that is executable on the server-side processor at run time to create the client-side code.

5. The system of claim 4, the server-side processor being further programmed to embed the at least one tag within content for the web page using a content management system.

6. The system of claim 4, the server-side processor being further programmed to provide the at least one tag that is executable on the server-side processor at run time to create client-side widget code.

7. The system of claim 3, the server-side processor being further programmed to automatically generate the client-side code at run time that is executable on the client-side processor.

8. The system of claim 7, the server-side processor being further programmed to automatically generate the client-side code at run time that is executable on the client-side processor running a client-side browser.

9. The system of claim 8, the server-side processor being further programmed to automatically generate the client-side code by the at least one tag at run time, the client-side code being executable on the client-side processor running the client-side browser.

10. The system of claim 9, the server-side processor being further programmed to automatically generate the client-side code by the at least one tag at run time that is executable on the client-side processor running the client-side browser as a component of the web page with dynamic behavior.

11. The system of claim 10, the server-side processor being further programmed to automatically generate the client-side code by the at least one tag at run time that is executable on the client-side processor running the client-side browser as the component of the web page with dynamic behavior that refreshes itself.

12. The system of claim 11, the server-side processor being further programmed to automatically generate rich Internet application code that is executable on the client-side processor running the client-side browser as the component of the web page with dynamic behavior that refreshes itself.

13. The system of claim 3, the server-side processor being further programmed to automatically download multiple functions in the client-side code simultaneously to the client side processor using a non-blocking mechanism.

14. The system of claim 13, the server-side processor being further programmed to automatically download the multiple functions in the client-side code simultaneously to the client-side processor using a JavaScript non-blocking mechanism.

15. The system of claim 1, said client-side processor being further programmed to execute the client-side code to become a widget displayed as a main body of the web page on the display screen of the client-side computing device.

16. The system of claim 1, said client-side processor being further programmed to trigger the dynamic behavior of the client-side code by the occurrence of a user interaction on the web page.

17. The system of claim 16, said client-side processor being further programmed to trigger the dynamic behavior of a rich Internet application component by the occurrence of the user interaction on the web page.

18. The system of claim 1, said client-side processor being further programmed to dynamically change properties of the client-side code on the server-side processor based on the occurrence of the at least one event.

19. The system of claim 1, said client-side processor being further programmed to automatically update content of the widget by the widget to reflect the occurrence of the at least one event.

20. The system of claim 19, said client-side processor being further programmed to automatically update content of the widget by the widget to reflect the occurrence of the at least one event without affecting any other content on the web page.

21. The system of claim 1, said client-side processor being further programmed to register the by widget in an event handler mechanism for the occurrence of the at least one event.

22. The system of claim 1, said client-side processor being further programmed to redisplay the widget from the server-side processor as a component of the web page on the subsequent occasion with a change in the widget without regenerating the client-side code.

23. A method, comprising:

executing, by a client-side computing device processor coupled to memory, client-side code for content of a web page embedded with at least one tag to become a widget with dynamic behavior attributes as a component of the web page on a display screen of the client-side computing device;

triggering, by the client-side computing device processor, dynamic behavior of the client-side code for the content of the web page embedded with the at least one tag via the dynamic behavior attributes of the widget by an occurrence of an event based at least in part on a user interaction with the client-side computing device processor;

caching, by the client-side computing device processor on a server-side processor communicably coupled to the client-side computing device processor, the client-side code for the content of the web page embedded with the at least one tag according to a tag parameter when a change is implemented in the widget by said occurrence of the event; and

redisplaying, by the client-side computing device processor, the widget on the display screen of the client-side computing device with the change implemented in the widget as the component of the web page on a subsequent occasion without regenerating the client-side code.

24. A non-transitory computer-readable storage medium with an executable program stored thereon, wherein the program instructs a processor of a client-side computing device to:

execute client-side code for content of a web page embedded with at least one tag to become a widget with dynamic behavior attributes as a component of the web page on a display screen of the client-side computing device;

trigger dynamic behavior of the client-side code for the content of the web page embedded with the at least one tag via the dynamic behavior attributes of the widget by an occurrence of an event based at least in part on a user interaction with the client-side computing device processor;

cache, on a server-side processor communicably coupled to the client-side computing device processor, the client-side code for the content of the web page embedded with the at least one tag according to a tag parameter when a change is implemented in the widget by said occurrence of the event; and

redisplay the widget on the display screen of the client-side computing device with the change implemented in the widget as the component of the web page on a subsequent occasion without regenerating the client-side code.