|Publication number||US6735741 B1|
|Application number||US 09/364,680|
|Publication date||May 11, 2004|
|Filing date||Jul 30, 1999|
|Priority date||Jul 30, 1999|
|Publication number||09364680, 364680, US 6735741 B1, US 6735741B1, US-B1-6735741, US6735741 B1, US6735741B1|
|Inventors||Jatinder Singh Pannu|
|Original Assignee||International Business Machines Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (8), Referenced by (61), Classifications (26), Legal Events (5)|
|External Links: USPTO, USPTO Assignment, Espacenet|
1. Field of the Invention
The present invention relates to a method, system, and program for dynamically linking to data when copies are maintained at different storage locations and, in network environments, linking to an alternate server including a copy of the data.
2. Description of the Related Art
In a client/server network environment, data is distributed at different storage locations. Users accessing files or database records will use a fixed file path name to access the data. There are many software techniques used in the art for allowing users to access or link to a document at a distributed location, such as a file server. In the Internet context, a hypertext link may be embedded in a Hypertext Markup Language (HTML) document that provides a Universal Resource Locator (URL) of the linked document, which is the global address of a document on the World Wide Web. The document may then be retrieved via this hypertext link that uses the address of the document on a server connected to the Internet or World Wide Web. For instance, an HTML page may include hypertext links to other HTML pages of interest.
Further, most WINDOWS applications enable object linking and embedding (OLE) between applications and between documents. Hyptertext linking and embedding is used as a method of sharing data between documents. This allows immediate access to the current version of the linked embedded document. For instance, in the LOTUS NOTES** environment, a document or an e-mail message may contain a document link (doclink) to another document stored at a location in the network. With Lotus Notes, links can be created to documents, views, and databases. Links appear as a graphical representation or icon of a piece of paper with a corner folded down. Associated with each link is a location, called the link pointer, within the link document. When the user double-clicks the link, Lotus Notes displays the link document showing the section of text containing the link pointer. When the user closes the link document, Lotus Notes returns to the original document that contained the link. These links or icons representing the links may be included in e-mails or any other Lotus Notes documents.
The links created in HTML pages, Lotus Notes, and other systems are static links. If the database ID or document ID referenced in the link is available at a different location, then another hypertext link to the new location of the document will have to be created to address the file or data at this new location.
In network systems, especially those distributed world wide, data may be replicated at different server locations. Lotus Notes allows multiple copies of a single file, called replicas, on multiple servers or workstations. This allows users at dispersed locations to access the same data from a local file server. A replica differs from a copy of a file, in that the original file and its replica have the same replica ID number. Replication is the process of sharing changes between replicas. Lotus Notes applies updates to the master copy of the data to the replicas to insure consistency between the replicas and the master copy of the data.
Although replicas of databases may be maintained, when a user activates a link, the linked document is accessed at the server initially specified when the link is created as document addressed by the link is static. i.e., points to the same document. Thus, even if the data is at a more proximate replicated location, the link will access the data at the server initially specified and ignore the presence of the data at a more proximate replica location.
There is thus a need in the art for an improved method, system, and program for providing links to data within documents.
To overcome the limitations in the prior art described above, preferred embodiments disclose a system, method, and program for linking to data from a document that includes a pointer to the data in a first storage device. A first request to access the data addressed by the pointer in the document is processed. Information on alternate storage devices and data therein is processed to determine whether a copy of the data is present in a second storage device. A second request is submitted to access the copy of the data in the second storage device after determining that the information indicates that the second storage device includes the data. The accessed copy of the data, received in response to the second request, is then returned to the first request.
In further embodiments, the document is opened and a user selectable graphical representation of the pointer to the data in the opened document is displayed. In such case, the first request is generated in response to user selection of the graphical representation of the pointer to the data.
In network embodiments, a first computer includes the document including a pointer to data at a second computer. A first request is processed to access the data addressed by the pointer in the document. Information on alternate computers and data therein is processed to determine whether a copy of the data is present in a third computer. The first, second, and third computers communicate over a network. A second request is submitted to the third computer for the copy of the data after determining that the third computer maintains the copy of the data. The accessed copy of the data, received in response to the second request, is returned to the first request.
In further network embodiments, the data is included in a database. The information on alternate computers indicates different domains, servers included in each domain, and at least one database included in each server. In such case, a determination is made of a domain indicated in the information having the same domain as the first computer. A determination is then made as to whether one server in the determined domain that includes a copy of the database including the copy of the data addressed by the pointer in the document. In such case, submitting the second request comprises submitting the second request to the determined server including the copy of the database.
In still further network embodiments, location information may be provided on the location of the alternate computers to allow the selection of a server including the copy of the database that is at the most proximate location to the first computer.
In further embodiments, the information on alternate storage devices and servers may be maintained in the document including the pointer to the data.
Preferred embodiments provide a mechanism for allowing the automatic selection of an alternate location to access data embedded in a document different from the address specified by the link. Typically, when an embedded link to data within a document is processed, the link is static and the same address specified by the link is accessed to retrieve the data. Preferred embodiments provide information that may be used to access the data at a more proximate storage device or network server than the location specified in the link. This provides dynamic smart linking to the closest location that includes the linked data. This invention is especially useful in network environments where data is replicated at servers in dispersed geographical locations. In such environments, the preferred embodiments will automatically access data addressed in a link within a document, such as a hypertext link, from the most proximate geographical location.
Referring now to the drawings in which like reference numbers represents corresponding parts throughout:
FIG. 1 illustrates a computing environment in which preferred embodiments in accordance with the present invention are implemented;
FIG. 2 illustrates a look-up table of available databases and servers in the system at different locations in accordance with preferred embodiments of the present invention;
FIGS. 3a, b illustrates logic to use a link to access a document in a network computing environment in accordance with the present invention are implemented;
In the following description, reference is made to the accompanying drawings which form a part hereof, and which illustrate several embodiments of the present invention. It is understood that other embodiments may be utilized and structural and operational changes may be made without departing from the scope of the present invention.
FIG. 1 illustrates a hardware and software environment in which preferred embodiments are implemented. A computing environment 2 comprises servers 4 and 6, a client computer 8, and a network 10 providing communication there between. The servers 4 and 6 may be any server device known in the art capable of servicing network and e-mail requests, e.g., IBM NETFINITY, AS/400, RS/6000, etc.** The client 8 may be comprised of any computing device known in the art that is capable of accessing and retrieving information from a network. In preferred embodiments, the servers 4, 6 include messaging, application, and data server software, such as the LOTUS DOMINO software,** to provide messaging, such as e-mail messages, application programs, and data to one or more clients 8. The client 8 would include client software capable of interfacing with the servers 4, 6, such as the LOTUS NOTES** software, which provides users a graphical user interface (GUI) to access the data from the servers 4, 6, and databases 12 a and 12 b in the servers 4 and 6. Further details of the Lotus server and client architecture are described in the publication “Lotus Domino Release 5.0:A Developer's Handbook,” IBM document no. SG24-5331-00 (Copyright IBM Corp., January 1999), which publication is incorporated herein by reference in its entirety.
The network 10 may be a TCP/IP network, such as an Intranet, the Internet, World Wide Web, or any other network system known in the art, e.g., LAN, Ethernet, WAN, System Area Network (SAN), Token Ring, LocalTalk, TCP/IP, the Internet, etc. Alternatively, there may be separate and different networks between the servers 4 and 6 and client 8.
The servers 4 and 6 further include a storage area, e.g., hard disk drive, tape drive, cache, etc., to store files, databases, and any other applications and data objects. The servers 4 and 6 include databases 12 a and 12 b, respectively. In preferred embodiments, database 12 b in server 6 is a replica of the database 12 a in server 4. In the Lotus Notes environment, a database replica is an exact copy of a database. Multiple replicas of a single database may be maintained on multiple servers. By using distributed replicas, users can access the same information on different networks, in different time zones, or even in different countries, without having to access one centrally located database. A database replica and the original database share the same replica ID, a unique number assigned to each database. During replication, a database on one server transfers any new, edited, or deleted documents and design elements to a database on another server or workstation. Data can be transferred from one server to another, back and forth between servers, or between a server and workstation. Because replication is incremental, transferring only changes to a database, the amount of network traffic and server time involved in synchronizing databases is minimized. Replication automatically distributes and synchronizes information and applications across geographically dispersed sites. In preferred embodiments, servers 4 and 6 are in geographically dispersed sites. Thus, database 12 b provides a mirror replication of the data in database 12 a at a different geographical location to make the data available to users at the different geographical location.
The client 8 accesses a document 14, which may be a form, e-mail message, or any other type of document maintained locally or received from another system in the network 10. The document 14 includes an embedded link 16 that addresses a document 18 in database 12 a in server 4. The document 18 may be a file, such as a text, image, sound file, motion picture, etc., or a portion of a database, thereby providing a view into certain database records. This link 16 may be in the form of a hypertext link, including the URL address of the document 18 or a Lotus Notes Doculink. The link 16 may be a graphically displayed link, such as the HTML hypertext link or the Lotus Notes doculink, or an embedded link that is not displayed and accesses the document 18 when the document 14 is opened. In the Lotus Notes environment, the form or document 14 includes fields of information on the document 18 to allow a script program executed in response to selection of the link 16 to access and display the document 18 from document 14. These fields embedded into the document 14, described below, are not displayed, but used to access the document 18 to display within document 14:
Document Server—indicates the server that includes the linked document 18.
Document Database—indicates the database that includes the linked document 18.
Document ID—the uniquely referenced information object within the database, i.e., the document 18.
Domains—provides a list of domains available in the network 10. A domain is a collection of servers and clients/users that share a common directory. The primary function is mail routing. Users' domains are determined by the location of their server-based mail files.
Locations—provides geographical locations within each of the domains indicated in the Domains field. The location name field may further include a short or abbreviated form of the name.
Data Servers—indicates the servers included in each of the locations of each of the domains indicated in the Domains and Locations fields.
Data Bases—indicates the databases included in each of the servers indicated in the Data Servers' field.
Default Domain—indicates the domain of the master database including the linked-to document 18. In systems with one or more replica servers, the Default Domain field indicates the domain of the master server from which the replica servers are derived. The Default Domain field may include a short or abbreviated form of the domain name.
Default Data Server—indicates the master server, e.g., server 4, within the master or default domain, from which the replica servers, e.g., server 6, are generated.
Default Database—indicates the master database, e.g., database 12 a, within the master or default domain, from which the replica databases, e.g., database 12 b, are generated.
The Document Server, Document Database, and Document ID fields include the information to address the document addressed by the link 16, including server, database, and unique document ID of the document 18 for which the link was created. This information is used to access the document 18 from document 14. Users may execute the link 16 by selecting an icon, which in Lotus Notes is a graphical page or button, that causes execution of a script program that processes the information in the Document Server, Document Database, and Document ID fields in the document 16 to access the document 18 for display at the client 8.
The Domains, Locations, Data Servers, and Database fields provide the information the client 8 needs to access an alternative, more proximate, replica server, e.g., server 6, including the document 18. These fields form a table or association of domains to locations, domains to data servers, and databases to servers. FIG. 2 illustrates a look-up table 30 that may be formed from the data in these fields. As can be seen, in look-up table 30, server 4 in Location C in Domain 2, includes replicas of the databases 1, 2, and 3 also maintained in Server 1 at Location A.
The Default Domain, Default Data Server, and Default Database fields indicate the location of the master data for the database from which replicas are derived. This location may be different than the location specified in the Document Server, Document Database, and Document ID if the link was created from a server other than the default server including the master database.
When creating a message or document 14 including the link 16, a member in the network 10, i.e., a client or server, would include a graphical element link and information on the location of the document 18 subject to the link in the Document Server, Document Database, and Document ID fields included in the message or document 14. The creator of the message would also include information on alternate servers 6 in the Domains, Locations, Data Servers, and Database fields of the message/document 14. In this way, information on alternative locations of the database 12 a is embedded within the document 14 including the link 16. In the Lotus Notes environment, these fields would be included in the fields of a Lotus Notes form, and not displayed. In the HTML environment, the information on alternate locations of the database 12 a would be embedded in the HTML document and accessed by the HTML browser to determine an alternate location from which to access the document.
Preferred embodiments include a link program resident in software within the client 8 to process the information in the above fields to access the file or data from the location used to create the link or from a more proximate location containing a replica of the linked-to data. This link program may be provided as a component with the program that processes the document including the link, such as the HTML browser, Lotus Notes, etc. As discusses, the document 14 would include a graphical representation of the link, which may be a push button or other display mechanism, to cause the client 8 to execute the link program to retrieve the linked-to document 18. Execution of the program link would initiate the logic illustrated in FIGS. 3a, b, beginning at block 100. The link program determines (at block 102) the domain and location of the client 8 from which the link 16 was executed. This information may be determined from the mail domain used by the client 8. The link program then processes (at block 104) the Domains field, indicating available domains in the network 10, to determine (at block 106) whether there is a domain in the Domains field that is the same domain as the client 8. If not, the link program accesses (at block 108) the document having the ID indicated in the Document ID field at the server and database indicated in the Document Server and Database fields. At block 108, the link program accesses the document at the location of the document used to create the link. In this way, if there is no domain in the Domain field matching the client 8 domain, the link program uses the initially provided address of the link.
If there is a domain in the Domain field that matches the client 8 domain, then the link program processes (at block 110) the Database Field to determine (at block 112) whether there are identical databases including the database indicated in the Document Database field. The link program may determine replicas by determining (at block 112) whether any of the databases in the Database field have the same replica ID as the database indicated in the Document Database field. The replica ID is a property associated with the database. If there are no replicas, then control transfers to block 108 to access the document at the initial location for which the link was created, indicated in the Document Server and Database fields.
If there is a domain in the Domain field that matches the client 8 domain, then the link program processes (at block 114) the Data Servers field to determine servers that include a replica of the database indicated in the Document Database field. For those determined servers, the link program then processes (at block 118) the Locations field to find the determined server that is at the closest location to the client 8, e.g., server 6, which is different from the server 4 including the document that the link 16 addresses. This may be determined by first determining whether there is a server at the same location; if not, then programing methods known in the art may be used to determine the closest of any non-identical locations. After determining the most proximate server, the link program issues (at block 120) a request to retrieve the document 18 from the determined server 6 and replicated database 12 b therein having the ID indicated in the Document ID field. If the document 18 cannot be accessed from the determined most proximate server, then the link program accesses (at block 124) the document 18 having the document field from the server and database indicated in the Default Data Server and Default Database fields respectively. In this way, if the determined closest replica database is unavailable, then the link program accesses the document from the master copy. Otherwise, if the document 18 can be accessed from the most proximate replica, then the document 18 is accessed (at block 126) from such proximate server 6 and replica database 12 b.
With preferred embodiments, information is embedded within the document including the link, or embedded object, indicating alternative, more proximate locations that may include the document addressed by the link. For instance, if the client 8 and server 6 are located in Tokyo, Japan and the server 4 including the document 18 addressed by the link 16 are in Los Angeles, Calif., then the link program, using the information embedded in the document 14, would determine to access a copy of the document 18 from the local server 6 in Japan. In this way, the same link provides access to the most proximate, local version of the document, even if the link addresses the document at a distant location. For instance, HTML pages may be embedded with the information on different servers, and such information could be used to reroute a request initiated from user selection of a displayed hypertext link to a URL location to a more proximate URL location that contains a copy or replica of the requested document. In the Lotus Notes system, the information on different servers may be embedded in fields in an e-mail message or other Lotus Notes form, and then used to reroute a selection of a doculink addressing the document at a specific location to a more proximate location including a copy or replica of the requested document. With the preferred embodiments, users can access local database replicas of information by selecting the link that addresses the document at a more distant location.
The preferred embodiments will become especially useful as distributed computing paradigms and models are adopted in modern business processes, which often require replication of data throughout the world. Preferred embodiments, automatically and seamlessly router users of such distributed systems to the closest instance of the requested information in a transparent manner.
This concludes the description of the preferred embodiments of the invention. The following describes some alternative embodiments for accomplishing the present invention.
The preferred embodiments may be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof. The term “article of manufacture” (or alternatively, “computer program product”) as used herein is intended to encompass one or more computer programs and data files accessible from one or more computer-readable devices, carriers, or media, such as a magnetic storage media, “floppy disk,” CD-ROM, a file server providing access to the programs via a network transmission line, holographic unit, etc. Of course, those skilled in the art will recognize that many modifications may be made to this configuration without departing from the scope of the present invention.
Preferred embodiments were described as including information fields in the document providing the link which are processed to allow a program to access the linked-to document at the most proximate server in the domain. In further embodiments, these fields may be maintained in any data structure format known in the art, such as tables, trees, etc., to represent available and alternate domains, servers, and databases from which the linked-to file may be accessed.
Preferred embodiments were described with respect to a graphical representation of a hypertext link. However, in further embodiments, the link may not be a hypertext link, but a link that is not displayed and/or automatically accessed when the document is opened or read.
Preferred embodiments described the information needed to access alternative locations as embedded or overloaded into HTML and Lotus Notes type documents. However, such information may be included as an attribute of any document type accessed over a network from a remote location. Such information added to the document is available for execution by local programs when the user selects, e.g., clicks, the hypertext link.
Preferred embodiments were described with respect to Lotus Notes or HTML documents or messages including an embedded link to another document on a server in the system. However, the document may be in alternative file formats, such as Dynamic Hypertext Mark-Up Language (DHTML), the Extensible Markup Language (XML), Cascading Sytle Sheets, any other Standard Generalized Markup Language (SGML), or any document format known in the art.
Preferred embodiments were described with respect to a network environment in which the linked documents are provided to a client from a server over a network, such as the Internet or Intranet. However, in alternative embodiments the linked-to document and replica copies of the document may be maintained within storage devices managed by a single computing device, such as a hard disk drive and removable storage device managed by the single computer. In such case, the request for the document may be rerouted to a storage device having a higher data transfer rate than the storage device including the document addressed by the hypertext link, wherein all storage devices are managed by the same computer.
In summary, the present invention provides a system, method, and program for linking to data from a document that includes a pointer to the data in a first storage device. A first request to access the data addressed by the pointer in the document is processed. Information on alternate storage devices and data therein is processed to determine whether a copy of the data is present in a second storage device. A second request is submitted to access the copy of the data in the second storage device after determining that the information indicates that the second storage device includes the data. The accessed copy of the data, received in response to the second request, is then returned to the first request.
The foregoing description of the preferred embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended.
WINDOWS is registered trademarks of Microsoft Corporation; OS/2, NETFINITY, AS/400, and RS/6000 are registered trademarks of International Business Machines Corporation; LOTUS DOMINO is a trademark and LOTUS NOTES is a registered trademark of the Lotus Development Corporation.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5412806||Aug 20, 1992||May 2, 1995||Hewlett-Packard Company||Calibration of logical cost formulae for queries in a heterogeneous DBMS using synthetic database|
|US5742598 *||Oct 19, 1995||Apr 21, 1998||International Business Machines Corp.||Network for efficiently locating resources and routing service requests received from individual node connections|
|US5751961||Jan 31, 1996||May 12, 1998||Bell Communications Research, Inc.||Integrated internet system for translating logical addresses of internet documents to physical addresses using integrated service control point|
|US5765171 *||Dec 29, 1995||Jun 9, 1998||Lucent Technologies Inc.||Maintaining consistency of database replicas|
|US5802265||Dec 1, 1995||Sep 1, 1998||Stratus Computer, Inc.||Transparent fault tolerant computer system|
|US6223209 *||Sep 30, 1997||Apr 24, 2001||Ncr Corporation||Distributed world wide web servers|
|US6304913 *||Nov 9, 1998||Oct 16, 2001||Telefonaktiebolaget L M Ericsson (Publ)||Internet system and method for selecting a closest server from a plurality of alternative servers|
|US6389462 *||Dec 16, 1998||May 14, 2002||Lucent Technologies Inc.||Method and apparatus for transparently directing requests for web objects to proxy caches|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US6965926 *||Apr 10, 2000||Nov 15, 2005||Silverpop Systems, Inc.||Methods and systems for receiving and viewing content-rich communications|
|US7089295||Sep 5, 2001||Aug 8, 2006||Oracle International Corporation||Customizing content provided by a service|
|US7127705||Sep 5, 2001||Oct 24, 2006||Oracle International Corporation||Developing applications online|
|US7143140 *||Nov 17, 2003||Nov 28, 2006||Bellsouth Intellectual Property Corporation||Method and system for publishing an electronic file attached to an electronic mail message|
|US7386597 *||Apr 9, 2002||Jun 10, 2008||Hitachi, Ltd.||Contents distributing method and distributing system|
|US7424517||Nov 3, 2006||Sep 9, 2008||At&T Intellectual Property, I.L.P.||Method and system for publishing an electronic file attached to an electronic file attached to an electronic mail message|
|US7702790 *||Sep 14, 2001||Apr 20, 2010||Canon Kabushiki Kaisha||Network system available for simultaneous connections of plural pieces of equipment, advanced equipment in the system, method of using functions of another piece of equipment, and storage medium|
|US7730155||Oct 1, 2002||Jun 1, 2010||Apple Inc.||Method and apparatus for dynamically locating resources|
|US7730159 *||Dec 27, 2006||Jun 1, 2010||Apple Inc.||Method and apparatus for dynamically locating resources|
|US7747720||May 23, 2005||Jun 29, 2010||Cisco Technology, Inc.||Arrangement for selecting a server to provide distributed services from among multiple servers based on a location of a client device|
|US7765277 *||Dec 27, 2006||Jul 27, 2010||Apple Inc.||Method and apparatus for dynamically locating resources|
|US7774774||Oct 22, 2003||Aug 10, 2010||Apple Inc.||Software setup system|
|US7784030||Sep 30, 2005||Aug 24, 2010||Oracle International Corporation||Developing applications online|
|US7792989 *||Apr 21, 2005||Sep 7, 2010||Cisco Technology, Inc.||Arrangement for selecting a server to provide distributed services from among multiple servers based on a location of a client device|
|US7865564||Sep 9, 2008||Jan 4, 2011||At&T Intellectual Property I, L.P.||Method and system for publishing an electronic file attached to an electronic mail message|
|US7865579||Jul 10, 2006||Jan 4, 2011||Apple Inc.||Method and apparatus for administering the operating system of a net-booted environment|
|US8024652 *||Apr 10, 2007||Sep 20, 2011||Microsoft Corporation||Techniques to associate information between application programs|
|US8065378||Nov 30, 2010||Nov 22, 2011||At&T Intellectual Property I, L.P.||Method and system for publishing an electronic file attached to an electronic mail message|
|US8155122 *||Dec 21, 2007||Apr 10, 2012||Verizon Business Global Llc||Linking autonomous systems with dual premise routing domains|
|US8176484||Sep 29, 2006||May 8, 2012||Oracle International Corporation||One click deployment|
|US8195607 *||Aug 31, 2007||Jun 5, 2012||International Business Machines Corporation||Fail over resource manager access in a content management system|
|US8280973||Oct 2, 2012||At&T Intellectual Property I, L.P.||Method and system for publishing an electronic file attached to an electronic mail message|
|US8438562||Apr 24, 2012||May 7, 2013||Oracle International Corporation||One click deployment|
|US8566411||Sep 14, 2012||Oct 22, 2013||At&T Intellectual Property I, L.P.||Method and system for publishing an electronic file attached to an electronic mail message|
|US8631077 *||Jul 22, 2004||Jan 14, 2014||International Business Machines Corporation||Duplicate e-mail content detection and automatic doclink conversion|
|US8813067||Apr 30, 2013||Aug 19, 2014||Oracle International Corporation||One click deployment|
|US8838731 *||May 28, 2010||Sep 16, 2014||Apple Inc.||Method and apparatus for dynamically locating resources|
|US8966382 *||Sep 27, 2012||Feb 24, 2015||Emc Corporation||Managing production and replica copies dynamically|
|US9167051||May 7, 2013||Oct 20, 2015||Oracle International Corporation||Transforming condition-independent output into condition-dependent output|
|US9203789||Sep 20, 2013||Dec 1, 2015||At&T Intellectual Property I, L.P.||Method and system for publishing an electronic file attached to an electronic message|
|US20010027466 *||Mar 21, 2001||Oct 4, 2001||Nec Corporation||Electronic mail transfer device and system, electronic mail transfer method|
|US20020040399 *||Sep 14, 2001||Apr 4, 2002||Takayuki Nagashima||Network system available for simultaneous connections of plural pieces of equipment, advanced equipment in the system, method of using functions of another piece of equipment, and storage medium|
|US20020078168 *||Sep 5, 2001||Jun 20, 2002||Jacob Christfort||Developing applications online|
|US20020120684 *||Sep 5, 2001||Aug 29, 2002||Jacob Christfort||Customizing content provided by a service|
|US20020129016 *||Sep 5, 2001||Sep 12, 2002||Jacob Christfort||Accessing data stored at an intermediary from a service|
|US20020138617 *||Sep 5, 2001||Sep 26, 2002||Jacob Christfort||Providing content from multiple services|
|US20030115306 *||Dec 19, 2001||Jun 19, 2003||Richard Hagarty||Modification of map of storage area network resources|
|US20030126197 *||Dec 28, 2001||Jul 3, 2003||Black Brad R.||Efficient content placement using network proximity|
|US20030221162 *||Dec 14, 2001||Nov 27, 2003||Sridhar Mandayam Andampillai||Meta-templates in website development and methods therefor|
|US20030233281 *||Apr 9, 2002||Dec 18, 2003||Tadashi Takeuchi||Contents distributing method and distributing system|
|US20040098461 *||Nov 17, 2003||May 20, 2004||Dennis Gary J.||Method and system for publishing an electronic file attached to an electronic mail message|
|US20060020668 *||Jul 22, 2004||Jan 26, 2006||International Business Machines Corporation||System and method for duplicate e-mail content detection and automatic doclink conversion|
|US20060116988 *||Apr 21, 2005||Jun 1, 2006||John Toebes||Arrangement for selecting a server to provide distributed services from among multiple servers based on a location of a client device|
|US20060117020 *||Mar 17, 2005||Jun 1, 2006||John Toebes|
|US20060117038 *||May 23, 2005||Jun 1, 2006||John Toebes|
|US20060259596 *||Jul 10, 2006||Nov 16, 2006||Birse Cameron S||Method and apparatus for administering the operating system of a net-booted environment|
|US20070028234 *||Sep 29, 2006||Feb 1, 2007||Oracle International Corporation||One click deployment|
|US20070050462 *||Nov 3, 2006||Mar 1, 2007||Dennis Gary J||Method and system for publishing an electronic file attached to an electronic file attached to an electronic mail message|
|US20070078942 *||Sep 30, 2005||Apr 5, 2007||Jacob Christfort||Developing applications online|
|US20070294290 *||Aug 31, 2007||Dec 20, 2007||International Business Machines Corporation||Fail over resource manager access in a content management system|
|US20080095157 *||Dec 21, 2007||Apr 24, 2008||Verizon Business Global Llc||Linking autonomous systems with dual premise routing domains|
|US20080215710 *||Apr 30, 2008||Sep 4, 2008||Tadashi Takeuchi||Contents distributing method and distributing system|
|US20080256113 *||Apr 10, 2007||Oct 16, 2008||Microsoft Corporation||Techniques to associate information between application programs|
|US20090006573 *||Sep 9, 2008||Jan 1, 2009||Bellsouth Intellectual Property Corporation||Method And System For Publishing An Electronic File Attached To An Electronic Mail Message|
|US20100241728 *||Sep 23, 2010||Gordon Ross Meyer||Method and apparatus for dynamically locating resources|
|US20100250668 *||Jun 4, 2010||Sep 30, 2010||Cisco Technology, Inc.|
|US20100306760 *||Aug 9, 2010||Dec 2, 2010||Mulligan J Scott||Software setup system|
|US20110041177 *||Feb 17, 2011||Microsoft Corporation||Context-sensitive input user interface|
|US20110131489 *||Nov 30, 2010||Jun 2, 2011||At&T Intellectual Property I, L.P. Via Transfer From Bellsouth Intellectual Property Corporation||Method And System For Publishing An Electronic File Attached To An Electronic Mail Message|
|US20110172887 *||Jul 14, 2011||Reeve David R||Vehicle assembly control method for collaborative behavior|
|USRE45184||Feb 14, 2013||Oct 7, 2014||International Business Machines Corporation||Sectional E-mail transmission|
|U.S. Classification||715/234, 709/200, 709/219, 709/201, 709/203, 709/217, 709/238, 709/218, 709/229, 707/999.001, 707/999.01|
|International Classification||H04L29/08, H04L29/06, H04L29/12|
|Cooperative Classification||Y10S707/99931, H04L29/12594, H04L67/1002, H04L67/02, H04L69/329, H04L61/301, H04L29/12009|
|European Classification||H04L61/30C, H04L29/08N9A, H04L29/12A, H04L29/08N1, H04L29/12A5|
|Jul 30, 1999||AS||Assignment|
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PANNU, JATINDER SINGH;REEL/FRAME:010146/0281
Effective date: 19990729
|Sep 19, 2007||FPAY||Fee payment|
Year of fee payment: 4
|Sep 13, 2011||AS||Assignment|
Owner name: GOOGLE INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:026894/0001
Effective date: 20110817
|Sep 23, 2011||FPAY||Fee payment|
Year of fee payment: 8
|Nov 11, 2015||FPAY||Fee payment|
Year of fee payment: 12