US20050283462A1 - Files transfer between a remote home server and a local server - Google Patents

Files transfer between a remote home server and a local server Download PDF

Info

Publication number
US20050283462A1
US20050283462A1 US11/210,190 US21019005A US2005283462A1 US 20050283462 A1 US20050283462 A1 US 20050283462A1 US 21019005 A US21019005 A US 21019005A US 2005283462 A1 US2005283462 A1 US 2005283462A1
Authority
US
United States
Prior art keywords
file
server
local
client
home
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US11/210,190
Inventor
Jean-Francois Pennec
Jacques Fieschi
Alain Benayoun
Patrick Michel
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to US11/210,190 priority Critical patent/US20050283462A1/en
Publication of US20050283462A1 publication Critical patent/US20050283462A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/18—File system types
    • G06F16/182—Distributed file systems

Definitions

  • the present invention relates to files transfer between a remote server and a local server. Such a transfer is necessary when a user is temporarily connected to a local server different from a remote home server to which this user is usually connected.
  • TELNET A first method, allows a user connected to a network with a local computer to access a remote computer such that the local computer is a terminal of the remote computer.
  • the term TELNET refers to a remote connection on the INTERNET that is made with the TELNET protocol.
  • the local computer limits the interaction with the remote computer and the file management between both computers is not very practical. It is also possible to open an interactive session with TELNET. Accordingly, once the connection has been established, the local computer is transparent and the user works as if he were directly attached to the remote computer. During the session, both computers are connected, what means that access times could be long, especially when the remote computer is overburdened.
  • Directory replication Another method is known as directory replication, a feature offered by servers equipped with MICROSOFT WINDOWS NT (registered trademark).
  • Directory replication allows to set up and maintain identical directories on multiple stations such as servers or personal computers. Updates made to the files or directories on one server are periodically replicated to other stations in import directories. Replication is well adapted for read only files since import directories that receive copies of the files are overwritten each time replication occurs. Any modification made on a file in an import directory is lost at the next replication. Consequently, the user cannot be sure that the modifications he has made in an import directory will be saved; the saving procedure has to be done manually, by means of specific commands.
  • a method for providing a file comprises the following steps:
  • a method for transferring a file from a home server comprises the following steps:
  • this request comprising the home server identification
  • a method for sending back the file to the home server, wherein is stored an information according to which said file is locally stored comprises the following steps:
  • this method comprises a further step for sending an information to the home server when the file has not been locally modified.
  • FIG. 1 represents the equipments involved in the invention
  • FIG. 2 represents the main components of a local file server
  • FIG. 3 represents the main components of a home file server
  • FIG. 4 is a diagram showing the messages exchange between the client, the local server and the home server, and
  • FIG. 5 is a flow chart of the method used in the local server.
  • a personal computer or client 10 is connected to a local file server 11 by means of a local area network 12 itself connected to a wide area network 15 , generally with a router 14 .
  • a remote home file server 17 is also connected to the wide area network 15 such as Internet either directly or through another router (not shown) and another local area network (not shown).
  • the local file server 11 comprises a first LAN adapter, 21 where LAN means “Local Area Network”. This adapter is used to transmit and receive messages on the network with the client 10 and with the home file server 17 .
  • LAN Local Area Network
  • Another component of the local file server 11 is a first disk controller 22 such as a SCSI adapter (SCSI for “Small Computer System interface”) or a RAID adapter (RAID for “Redundant Array of Inexpensive Disks”).
  • the local server also comprises a first processor 23 to perform the method which will be described further.
  • the local file server 11 comprises in addition a first memory 25 which includes two specific tables, the local client table LT 1 and the guest client table GT 1 . Each entry in these tables corresponds to a user and gives a pointer on one directory called the directory file.
  • the remote home file server 17 is very similar to the local file server 11 . It comprises a second LAN adapter 31 , a second disk controller 32 , a second processor 23 and a second memory 35 .
  • This memory includes also a local client table LT 2 , a guest client table GT 2 and it further includes a remotely logged client table RT 2 .
  • the client or personal computer 400 When the client or personal computer 400 is powered on, it first runs the BIOS program 403 stored in a read only memory located in a LAN adapter.
  • the BIOS program performs a remote boot 406 on the local file server 401 , using any usual protocol such as DHCP (“Dynamic Host Configuration Protocol”) or BOOTP (“Bootstrap protocol”).
  • the BIOS program sends a Connection request 404 to the local server 401 which sends back a login application 405 .
  • the adapter of the personal computer 400 uses a file transfer protocol such as TFTP (“Trivial File Transfer Protocol”), FTP (“File Transfer Protocol”) or CIFS (“Common Investment File System”) for downloading this login file from the local server 401 .
  • the personal computer 400 runs the login file which prompts a user of this computer to enter a user identification and eventually a password 407 .
  • the local file server 401 checks whether the user is one of its clients or not referring to the first local client table LT 1 408 . Assuming the user is not one of its clients and is a guest, this user should be stored in the guest client table GT 1 if this not already done.
  • the local server now requests the user to enter a home file server identification 409 - 410 . When this identification is received, the local server forwards 411 the client request to the home file server 402 .
  • the home server checks 412 that the user is one of its clients (referring to the second local client table LT 2 for instance) and acknowledges 413 the local server to accept this user.
  • the home server informs the local server of the operating system files needed for this user. Usually, most of these files are available at the local server and therefore need not to be transferred between both servers.
  • the home server sends a file including user specific data.
  • the local server can transfer the operating files to the client station 414 and the personal computer 400 can perform the loading of the operating system 415 .
  • a test 51 determines whether the client (user) using the client station is a guest or a local known client.
  • the requested file is simply transmitted to the client 54 .
  • the local server first checks 52 whether the file is in the local client directory or not by means of the guest client table GT 1 .
  • the local server sends the file to the client 54 .
  • the local server If the file is not in the local server (“no” answer), the local server requests the file to the home server 53 , stores this file in its memory and its identification in the guest client table, and then forwards the file to the client.
  • the files modifications made by the client on the personal computer are saved in the local server, what is state of the art.
  • an indication that the file has been modified is stored in the guest client table. According to an optional feature, this indication is also forwarded to the home server.
  • the local server checks whether it has been modified or not.
  • the modified file is forwarded to the home server.
  • the file is deleted and the identification of this file is removed from the guest client table GT 1 .
  • the home file server 17 when a file has been requested by a first local server, or when according to the above mentioned optional feature a file is modified in this local server, a corresponding information is stored in the remotely logged client table RT 2 together with the identification of the local server. Thus, when later this file is requested again by the user from another server or from the home server itself, the home server first checks if it appears in the remotely logged client table RT 2 . If it is the case, this file is first requested to the local server identified in the table RT 2 and it is overwritten on the version stored in the home server. The information according to which the file is in the first local server is then deleted in the remotely logged client table RT 2 .

Abstract

A method and system for providing a file utilizing information according to which the file is locally stored when the file is received from a remote server are disclosed. According to one embodiment, a method is provided which comprises receiving a request for the file, where the request comprises data identifying the remote server. The described embodiment further comprises checking that the file is locally stored, forwarding the file to the remote server when the file has been locally modified, and deleting the information according to which said file is locally stored.

Description

    BACKGROUND OF THE INVENTION
  • 1. Technical Field
  • The present invention relates to files transfer between a remote server and a local server. Such a transfer is necessary when a user is temporarily connected to a local server different from a remote home server to which this user is usually connected.
  • 2. Description of the Related Art
  • It is now very common that someone who travels needs to have access to a set of files, system files, data files or application files. So, this person can bring a portable computer with him, all the necessary files being stored in this computer. It is often not very convenient to carry such an equipment. Moreover, nowadays, the files of a computer user are often stored on a server, the home server. In this case, the user has to transfer all his files on the portable computer and he can forget some of these files. Thus, solutions have been developed to allow a user to access transparently to his own computer from another personal computer, generally by means of a local server.
  • A first method, TELNET, allows a user connected to a network with a local computer to access a remote computer such that the local computer is a terminal of the remote computer. The term TELNET refers to a remote connection on the INTERNET that is made with the TELNET protocol. When using electronic mail or FTP, a file transfer protocol, the local computer limits the interaction with the remote computer and the file management between both computers is not very practical. It is also possible to open an interactive session with TELNET. Accordingly, once the connection has been established, the local computer is transparent and the user works as if he were directly attached to the remote computer. During the session, both computers are connected, what means that access times could be long, especially when the remote computer is overburdened.
  • Another method is known as directory replication, a feature offered by servers equipped with MICROSOFT WINDOWS NT (registered trademark). Directory replication allows to set up and maintain identical directories on multiple stations such as servers or personal computers. Updates made to the files or directories on one server are periodically replicated to other stations in import directories. Replication is well adapted for read only files since import directories that receive copies of the files are overwritten each time replication occurs. Any modification made on a file in an import directory is lost at the next replication. Consequently, the user cannot be sure that the modifications he has made in an import directory will be saved; the saving procedure has to be done manually, by means of specific commands.
    • SUMMARY OF THE INVENTION
  • It is therefore a general object of the present invention to provide for a method which allows to access a file in a remote computer from a local computer in an efficient way and to insure that any modification of this file is saved.
  • According to the invention, in a remote computer, a method for providing a file comprises the following steps:
  • receiving a request for this file,
  • identifying this file as being stored in a distant server,
  • requesting the distant server to send the file,
  • identifying this file as being used, and
  • forwarding this file.
  • Besides, in a local server, a method for transferring a file from a home server comprises the following steps:
  • receiving a request for this file, this request comprising the home server identification,
  • checking that this file is not locally stored,
  • requesting this file to the home server,
  • identifying the file as being locally used, and
  • forwarding said file.
  • A method for sending back the file to the home server, wherein is stored an information according to which said file is locally stored, comprises the following steps:
  • receiving a request for this file, the request comprising the home server identification,
  • checking that the file is locally stored,
  • forwarding the file to the home server when it has been locally modified, and
  • deleting the information according to which this file is locally stored.
  • Advantageously, this method comprises a further step for sending an information to the home server when the file has not been locally modified.
    • BRIEF DESCRIPTION OF THE DRAWINGS
  • Embodiments of the present invention are described below by way of example only with reference to the accompanying drawings, wherein:
  • FIG. 1 represents the equipments involved in the invention,
  • FIG. 2 represents the main components of a local file server,
  • FIG. 3 represents the main components of a home file server,
  • FIG. 4 is a diagram showing the messages exchange between the client, the local server and the home server, and
  • FIG. 5 is a flow chart of the method used in the local server.
    • DETAILED DESCRIPTION OF THE INVENTION
  • With reference to FIG. 1, a personal computer or client 10 is connected to a local file server 11 by means of a local area network 12 itself connected to a wide area network 15, generally with a router 14. In addition, a remote home file server 17 is also connected to the wide area network 15 such as Internet either directly or through another router (not shown) and another local area network (not shown).
  • With reference to FIG. 2, the local file server 11 comprises a first LAN adapter, 21 where LAN means “Local Area Network”. This adapter is used to transmit and receive messages on the network with the client 10 and with the home file server 17. Another component of the local file server 11 is a first disk controller 22 such as a SCSI adapter (SCSI for “Small Computer System interface”) or a RAID adapter (RAID for “Redundant Array of Inexpensive Disks”). The local server also comprises a first processor 23 to perform the method which will be described further.
  • The local file server 11 comprises in addition a first memory 25 which includes two specific tables, the local client table LT1 and the guest client table GT1. Each entry in these tables corresponds to a user and gives a pointer on one directory called the directory file.
  • With reference to FIG. 3, the remote home file server 17 is very similar to the local file server 11. It comprises a second LAN adapter 31, a second disk controller 32, a second processor 23 and a second memory 35. This memory includes also a local client table LT2, a guest client table GT2 and it further includes a remotely logged client table RT2.
  • With reference to FIG. 4, a file transfer between the home file server 17-402 and the client 10-400 will now be described. There is a set of messages between the client and the local server 11-401 and another set of messages between the local server and the home server. There is no direct exchange between the client 400 and the home server 402.
  • When the client or personal computer 400 is powered on, it first runs the BIOS program 403 stored in a read only memory located in a LAN adapter. The BIOS program performs a remote boot 406 on the local file server 401, using any usual protocol such as DHCP (“Dynamic Host Configuration Protocol”) or BOOTP (“Bootstrap protocol”). The BIOS program sends a Connection request 404 to the local server 401 which sends back a login application 405. The adapter of the personal computer 400 uses a file transfer protocol such as TFTP (“Trivial File Transfer Protocol”), FTP (“File Transfer Protocol”) or CIFS (“Common Investment File System”) for downloading this login file from the local server 401. Subsequently, the personal computer 400 runs the login file which prompts a user of this computer to enter a user identification and eventually a password 407. The local file server 401 checks whether the user is one of its clients or not referring to the first local client table LT1 408. Assuming the user is not one of its clients and is a guest, this user should be stored in the guest client table GT1 if this not already done. The local server now requests the user to enter a home file server identification 409-410. When this identification is received, the local server forwards 411 the client request to the home file server 402. In response, the home server checks 412 that the user is one of its clients (referring to the second local client table LT2 for instance) and acknowledges 413 the local server to accept this user. In addition, the home server informs the local server of the operating system files needed for this user. Usually, most of these files are available at the local server and therefore need not to be transferred between both servers. Eventually, the home server sends a file including user specific data. The local server can transfer the operating files to the client station 414 and the personal computer 400 can perform the loading of the operating system 415.
  • Additional information on Internet protocols can be found in a IBM Company publication entitled: TCP/IP tutorial and technical overview GG24-3376-05, October 1998, edited by the International Technical Support Organization.
  • With reference to FIG. 5, a file transfer 50 is now described from the local server. First, a test 51 determines whether the client (user) using the client station is a guest or a local known client.
  • If the client is a local known user (“no” answer), the requested file is simply transmitted to the client 54.
  • If the client is a guest and requests a new file transfer, the local server first checks 52 whether the file is in the local client directory or not by means of the guest client table GT1.
  • If the file is in the local server (“yes” answer), the local server sends the file to the client 54.
  • If the file is not in the local server (“no” answer), the local server requests the file to the home server 53, stores this file in its memory and its identification in the guest client table, and then forwards the file to the client. The files modifications made by the client on the personal computer are saved in the local server, what is state of the art. Moreover, an indication that the file has been modified is stored in the guest client table. According to an optional feature, this indication is also forwarded to the home server.
  • On the other hand, when this file is requested by the home server, the local server checks whether it has been modified or not.
  • If the file has not been modified (answer “no”), this information is forwarded to the home server.
  • If the file has been modified (answer “yes”), the modified file is forwarded to the home server. In any case, the file is deleted and the identification of this file is removed from the guest client table GT1.
  • In the home file server 17, when a file has been requested by a first local server, or when according to the above mentioned optional feature a file is modified in this local server, a corresponding information is stored in the remotely logged client table RT2 together with the identification of the local server. Thus, when later this file is requested again by the user from another server or from the home server itself, the home server first checks if it appears in the remotely logged client table RT2. If it is the case, this file is first requested to the local server identified in the table RT2 and it is overwritten on the version stored in the home server. The information according to which the file is in the first local server is then deleted in the remotely logged client table RT2.
  • It then appears that the latest version of the file is always available, either in the home server or in a server identified in a table of the home server.
  • The scope of the present invention is in no way limited to the above embodiments. In particular, any means or steps could be replaced by equivalent means, respectively steps.

Claims (4)

1-2. (canceled)
3. A method for providing a file, wherein is stored information according to which said file is locally stored when said file is received from a remote server, said method comprising the following steps:
receiving a request for said file, said request comprising said remote server identification,
checking that said file is locally stored,
forwarding said file to said remote server when said file has been locally modified, and
deleting the information according to which said file is locally stored.
4. The method according to claim 3 further comprising a step for sending said information to said remote server when said file has not been locally modified.
5-8. (canceled)
US11/210,190 1999-10-21 2005-08-23 Files transfer between a remote home server and a local server Abandoned US20050283462A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/210,190 US20050283462A1 (en) 1999-10-21 2005-08-23 Files transfer between a remote home server and a local server

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
EP99480113 1999-10-21
EP99480113.2 1999-10-21
US09/659,649 US7203735B1 (en) 1999-10-21 2000-09-12 Files transfer between a remote home server and a local server
US11/210,190 US20050283462A1 (en) 1999-10-21 2005-08-23 Files transfer between a remote home server and a local server

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/659,649 Division US7203735B1 (en) 1999-10-21 2000-09-12 Files transfer between a remote home server and a local server

Publications (1)

Publication Number Publication Date
US20050283462A1 true US20050283462A1 (en) 2005-12-22

Family

ID=35481820

Family Applications (2)

Application Number Title Priority Date Filing Date
US09/659,649 Expired - Fee Related US7203735B1 (en) 1999-10-21 2000-09-12 Files transfer between a remote home server and a local server
US11/210,190 Abandoned US20050283462A1 (en) 1999-10-21 2005-08-23 Files transfer between a remote home server and a local server

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09/659,649 Expired - Fee Related US7203735B1 (en) 1999-10-21 2000-09-12 Files transfer between a remote home server and a local server

Country Status (1)

Country Link
US (2) US7203735B1 (en)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030084128A1 (en) * 2001-11-01 2003-05-01 Flying Wireless, Inc. Local agent for remote file access system
US20070013942A1 (en) * 2005-07-14 2007-01-18 Konica Minolta Business Technologies, Inc. Data communication system, image processing device, and method for managing data in image processing device
US20080147745A1 (en) * 2005-12-19 2008-06-19 Wilkinson Anthony J Method and system for providing synchronization of directory data
EP2143005A1 (en) * 2007-04-27 2010-01-13 Hewlett-Packard Development Company, L.P. Method and system of separate file storage locations as unified file storage
US20120215747A1 (en) * 2010-04-28 2012-08-23 Huawei Technologies Co., Ltd. Data uploading method, data downloading method, and data system
US20130262668A1 (en) * 2012-03-28 2013-10-03 Kyocera Corporation Portable terminal device, data management method, and data management program
US9256353B2 (en) 2006-12-19 2016-02-09 Vmware, Inc. Providing application and device management using entitlements
US11277381B2 (en) 2020-04-30 2022-03-15 Kyndryl, Inc. Multi-channel based just-in-time firewall control

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6192408B1 (en) * 1997-09-26 2001-02-20 Emc Corporation Network file server sharing local caches of file access information in data processors assigned to respective file systems
US7934251B2 (en) * 1999-12-02 2011-04-26 Western Digital Technologies, Inc. Managed peer-to-peer applications, systems and methods for distributed data access and storage
US7398382B2 (en) * 2004-12-29 2008-07-08 Intel Corporation Method and apparatus to enhance platform boot efficiency
US7991989B2 (en) * 2007-12-20 2011-08-02 Dell Product L.P. System and method for OS boot image provisioning based on user identity to enable mobile users
US9934050B2 (en) * 2014-12-17 2018-04-03 Quanta Computer Inc. System and method for network-based ISCSI boot parameter deployment

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5202971A (en) * 1987-02-13 1993-04-13 International Business Machines Corporation System for file and record locking between nodes in a distributed data processing environment maintaining one copy of each file lock
US5588147A (en) * 1994-01-14 1996-12-24 Microsoft Corporation Replication facility
US5812793A (en) * 1996-06-26 1998-09-22 Microsoft Corporation System and method for asynchronous store and forward data replication
US6233606B1 (en) * 1998-12-01 2001-05-15 Microsoft Corporation Automatic cache synchronization
US6308283B1 (en) * 1995-06-09 2001-10-23 Legato Systems, Inc. Real-time data protection system and method
US20040049294A1 (en) * 1999-09-23 2004-03-11 Agile Software Corporation Method and apparatus for providing controlled access to software objects and associated documents
US20050086384A1 (en) * 2003-09-04 2005-04-21 Johannes Ernst System and method for replicating, integrating and synchronizing distributed information
US7039860B1 (en) * 1999-10-01 2006-05-02 Netspinner Solutions As Creating web pages category list prior to the list being served to a browser

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5799147A (en) * 1994-10-19 1998-08-25 Shannon; John P. Computer recovery backup method
US5935207A (en) * 1996-06-03 1999-08-10 Webtv Networks, Inc. Method and apparatus for providing remote site administrators with user hits on mirrored web sites
US5926624A (en) * 1996-09-12 1999-07-20 Audible, Inc. Digital information library and delivery system with logic for generating files targeted to the playback device
US6182141B1 (en) * 1996-12-20 2001-01-30 Intel Corporation Transparent proxy server
US6516351B2 (en) * 1997-12-05 2003-02-04 Network Appliance, Inc. Enforcing uniform file-locking for diverse file-locking protocols
US6345266B1 (en) * 1998-12-23 2002-02-05 Novell, Inc. Predicate indexing for locating objects in a distributed directory
US6466970B1 (en) * 1999-01-27 2002-10-15 International Business Machines Corporation System and method for collecting and analyzing information about content requested in a network (World Wide Web) environment
US6272598B1 (en) * 1999-03-22 2001-08-07 Hewlett-Packard Company Web cache performance by applying different replacement policies to the web cache

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5202971A (en) * 1987-02-13 1993-04-13 International Business Machines Corporation System for file and record locking between nodes in a distributed data processing environment maintaining one copy of each file lock
US5588147A (en) * 1994-01-14 1996-12-24 Microsoft Corporation Replication facility
US6308283B1 (en) * 1995-06-09 2001-10-23 Legato Systems, Inc. Real-time data protection system and method
US5812793A (en) * 1996-06-26 1998-09-22 Microsoft Corporation System and method for asynchronous store and forward data replication
US6233606B1 (en) * 1998-12-01 2001-05-15 Microsoft Corporation Automatic cache synchronization
US20040049294A1 (en) * 1999-09-23 2004-03-11 Agile Software Corporation Method and apparatus for providing controlled access to software objects and associated documents
US7039860B1 (en) * 1999-10-01 2006-05-02 Netspinner Solutions As Creating web pages category list prior to the list being served to a browser
US20050086384A1 (en) * 2003-09-04 2005-04-21 Johannes Ernst System and method for replicating, integrating and synchronizing distributed information

Cited By (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9325774B2 (en) 2001-11-01 2016-04-26 Benhov Gmbh, Llc Local agent for remote file access system
US20060282521A1 (en) * 2001-11-01 2006-12-14 Sinotech Plc, L.L.C. Local agent for remote file access system
US9344482B2 (en) 2001-11-01 2016-05-17 Benhov Gmbh, Llc Local agent for remote file access system
US9332058B2 (en) * 2001-11-01 2016-05-03 Benhov Gmbh, Llc Local agent for remote file access system
US20030084128A1 (en) * 2001-11-01 2003-05-01 Flying Wireless, Inc. Local agent for remote file access system
US20100049721A1 (en) * 2001-11-01 2010-02-25 Anderson Jeffrey G Local Agent for Remote File Access System
US20070013942A1 (en) * 2005-07-14 2007-01-18 Konica Minolta Business Technologies, Inc. Data communication system, image processing device, and method for managing data in image processing device
US8245129B2 (en) * 2005-12-19 2012-08-14 Vmware, Inc. Method and system for providing synchronization of directory data
US10338969B2 (en) 2005-12-19 2019-07-02 Vmware, Inc. Managing a virtualized application workspace on a managed computing device
US10198162B2 (en) 2005-12-19 2019-02-05 Vmware, Inc. Method for installing or upgrading an application
US9317333B2 (en) 2005-12-19 2016-04-19 Vmware, Inc. Method and system for providing load balancing for virtualized application workspaces
US11194627B2 (en) 2005-12-19 2021-12-07 Vmware, Inc. Managing a virtualized application workspace on a managed computing device
US20080147787A1 (en) * 2005-12-19 2008-06-19 Wilkinson Anthony J Method and system for providing load balancing for virtualized application workspaces
US20080147745A1 (en) * 2005-12-19 2008-06-19 Wilkinson Anthony J Method and system for providing synchronization of directory data
US9841882B2 (en) 2006-12-19 2017-12-12 Vmware, Inc. Providing application and device management using entitlements
US9256353B2 (en) 2006-12-19 2016-02-09 Vmware, Inc. Providing application and device management using entitlements
EP2143005A1 (en) * 2007-04-27 2010-01-13 Hewlett-Packard Development Company, L.P. Method and system of separate file storage locations as unified file storage
EP2143005A4 (en) * 2007-04-27 2012-07-11 Hewlett Packard Development Co Method and system of separate file storage locations as unified file storage
US20120215747A1 (en) * 2010-04-28 2012-08-23 Huawei Technologies Co., Ltd. Data uploading method, data downloading method, and data system
US20130262668A1 (en) * 2012-03-28 2013-10-03 Kyocera Corporation Portable terminal device, data management method, and data management program
US11277381B2 (en) 2020-04-30 2022-03-15 Kyndryl, Inc. Multi-channel based just-in-time firewall control

Also Published As

Publication number Publication date
US7203735B1 (en) 2007-04-10

Similar Documents

Publication Publication Date Title
US20050283462A1 (en) Files transfer between a remote home server and a local server
US20210400112A1 (en) Redundant storage gateways
US6085192A (en) System and method for securely synchronizing multiple copies of a workspace element in a network
US5991813A (en) Network enabled SCSI interface
JP4311636B2 (en) A computer system that shares a storage device among multiple computers
US7240098B1 (en) System, method, and software for a virtual host bus adapter in a storage-area network
US5948108A (en) Method and system for providing fault tolerant access between clients and a server
US7080134B2 (en) Systems and methods for software distribution and management
US6473783B2 (en) Method and apparatus for sharing peripheral devices over a network
US6282563B1 (en) Agent moving method, message transmission method, agent transmission method, agent acquisition method, message acquisition method and agent list acquisition method, and computer
US6009474A (en) Method and apparatus for re-assigning network addresses to network servers by re-configuring a client host connected thereto
US20050132341A1 (en) Storage management software bridges
JPH08263417A (en) Method for accessing to independent resource of computer network and network subsystem
GB2330430B (en) Error handler for a proxy server computer system
JPS62118465A (en) Propagation of resource information
CN110445873B (en) Cloud platform service access method and redirection server
JP4588024B2 (en) Transparent file movement using namespace replication
US20080294748A1 (en) Proxy between network file system version three and network file system version four protocol
US20040024808A1 (en) Wide area storage localization system
EP1181652B1 (en) Extended file system
US20050073991A1 (en) Multiple wireless device synchronization server
JP2001216187A (en) Method and device for making data coincident among devices
US20030233510A1 (en) Storage resource integration layer interfaces
US20080133609A1 (en) Object-based storage system for defferring elimination of shared file and method thereof
JP2002261794A (en) Host connecting device and method, and its program

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION