Browse Prior Art Database

Two-way Synchronizable Links

IP.com Disclosure Number: IPCOM000201644D
Publication Date: 2010-Nov-17
Document File: 1 page(s) / 41K

Publishing Venue

The IP.com Prior Art Database

Abstract

Resources often have links associated with them for convenient access to those resources. However, when the original location of the resource changes, the associated links for that resource, if not manually maintained are often broken. This can lead to any number of problems such as users not able to access web-pages through to complex servers not being able to start correctly. 2-way synchronisable links are disclosed, which provide an automatic solution to prevent broken links from occurring.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 58% of the total text.

Page 01 of 1

Two-way Synchronizable Links

Whenever a resource contains a link, e.g. a file system hard/soft links or even webpage hyperlinks, it is possible that the resource to which the link points is moved or even removed from the system. The result of this action is that, for example, an application can fail to run correctly because the executable to which the shortcut points cannot be found or a lot of time has to be spent in trying to find all the documents in which the link is referred (such as on a webpage). The present disclosure proposes a 2-way link system which preserves the integrity of links when a resource is moved.

    Whenever a pair of files, A and B, contain a 2-way link between them, the link is always correct on the same filesystem meaning that when either file is moved, the link to the other file is preserved.

The invention attempts to address 2 different forms of linking between resources and each is described separately below:
Scenario 1:

    A is a webpage which contains a link to B which is another webpage. When webpage B is moved, the link in webpage A becomes invalidated. The present disclosure proposes the following solution:
When the link in webpage A is created to point to webpage B, a link synchronizer request (LSR) is produced. The LSR is sent to a SYNCHRONIZER which will, when available and if possible, synchronize webpages A and B. To do this, the synchronizer will create a second link in webpage B to the link in webpage A. Consider now that webpage...