System, Method and Apparatus for Dynamically Identifying Pop-out Links in Networked Applications via Lookup

• US 20180052930A1
• Filed: 08/15/2017
• Published: 02/22/2018
• Est. Priority Date: 08/16/2016
• Status: Active Grant

• Current Assignee: Christopher Mark Balz
• Original Assignee: Christopher Mark Balz
• Inventors: Balz, Christopher Mark
• Granted Patent: US 11,194,867 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing
• CPC Class Codes: G06F 16/9558 Details of hyperlinks; Management of linked annotations
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications

Abstract

System, method, and apparatus for providing and using a centralized Link Metadata System to identify if navigational links are pop-out links, is provided. The present invention offers a Link Metadata System, available on the Internet, of metadata associated with any given, specific Internet domain and URL or URI path combination. Software browsing user agents on remote window servers are then configured with the ability to request metadata from the Link Metadata System indicating that a link is a pop-out link. Upon receiving metadata, the user agent determines whether to perform navigation as normal or perform the pop-out link functionality of reloading the remote client web browser'"'"'s top level container with the content provided at the link'"'"'s destination URL or URI.

Claims

1. A computer-implemented method comprising:

upon navigation action on a link by a client web browser that is browsing a remote graphical computer desktop, remote graphical application window, or remote graphical windowing user session;

a) Sending a request for metadata to a lookup server;

b) Looking up metadata, using the link, in a lookup server registry;

c) Receiving, from the lookup server, a response with a payload of the requested metadata, indicating that the link is a pop-out link;

d) Sending a directive to the client web browser to reload the client web browser'"'"'s top level container with content provided at the pop-out link'"'"'s destination URL or URI.

2. The method of claim 1, wherein the user on the client web browser is a human user.

3. The method of claim 1, wherein the user on the client web browser is a search engine web crawler.

4. The method of claim 1, wherein the lookup server resides on the same physical or virtual computer as a DNS server.

5. The method of claim 1, wherein the lookup server is integrated programmatically into a DNS server, or vice-versa.

6. The method of claim 1, wherein the request for metadata is an http get request.

7. The method of claim 1, wherein the client web browser is directed to load a whole web page context into a child of itself, new or preexisting, leaving a client parent container unaltered by the navigation action.

8. The method of claim 7, wherein the child of the parent container is an HTML frame.

9. The method of claim 7, wherein the child of the parent container is a browser window or tab.

10. A Link Metadata System comprising at least one processor, the at least one processor configured to cause the system to at least perform:

Upon navigation action on a link by a client web browser that is browsing a remote graphical computer desktop, remote graphical application window, or remote graphical windowing user session;

a) Sending a request for metadata to a lookup server;

b) Looking up metadata, using the link, in a lookup server;

c) Receiving, from the lookup server, a response with a payload of the requested metadata, carrying a flag indicating that the link is a pop-out link;

d) Sending a directive to the client web browser to reload the client web browser'"'"'s top level container with content provided at the pop-out link'"'"'s destination URL or URI.

11. The system of claim 10, wherein the user on a client web browser is a human user.

12. The system of claim 10, wherein the user on a client web browser is a search engine web crawler.

13. The system of claim 10, wherein the lookup server resides on the same physical or virtual computer as a DNS server.

14. The system of claim 10, wherein the lookup server is integrated programmatically into a DNS server, or vice-versa.

15. The system of claim 10, where in the request for metadata is an http get request.

16. A Link Metadata server apparatus comprising:

At least one processor;

A registry of link addresses, each link address associated with a set of metadata;

wherein a request from a client for link metadata is looked up in the registry, said metadata indicating that the link is a pop-out link.

17. The apparatus of claim 16 further comprising a means for sending the looked-up link metadata to the client.

18. The apparatus of claim 16 further comprising a DNS server resident on the apparatus.

19. The apparatus of claim 16 further comprising a DNS server integrated programmatically.

20. The apparatus of claim 16, wherein the request from a client is an http get request.