CN104601724A - Method and system for uploading and downloading file - Google Patents

Method and system for uploading and downloading file Download PDF

Info

Publication number
CN104601724A
CN104601724A CN201510057145.XA CN201510057145A CN104601724A CN 104601724 A CN104601724 A CN 104601724A CN 201510057145 A CN201510057145 A CN 201510057145A CN 104601724 A CN104601724 A CN 104601724A
Authority
CN
China
Prior art keywords
magnetic disc
file
server
request
path
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.)
Granted
Application number
CN201510057145.XA
Other languages
Chinese (zh)
Other versions
CN104601724B (en
Inventor
杨爱民
龙晓春
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.)
Beijing Jinher Software Co Ltd
Original Assignee
Beijing Jinher Software Co Ltd
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 Beijing Jinher Software Co Ltd filed Critical Beijing Jinher Software Co Ltd
Priority to CN201510057145.XA priority Critical patent/CN104601724B/en
Publication of CN104601724A publication Critical patent/CN104601724A/en
Application granted granted Critical
Publication of CN104601724B publication Critical patent/CN104601724B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/02Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/06Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/565Conversion or adaptation of application format or content
    • H04L67/5651Reducing the amount or size of exchanged application data

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The invention belongs to the field of file services, and specifically relates to method and system for uploading and downloading a file. The method and system are that a downloading request from a client is queried and downloaded by layers through a CDN server, an IIS Web server, a database server and a disk server; with the adoption of the server combined querying method, the file downloading speed is greatly raised; the client sends the uploading request to the IIS Web server, the database server and the disk server to quickly upload the specified file; in addition, discontinuous downloading and uploading are supported, namely, large files can be downloaded or uploaded by segmentation due to the influences such as network cause, and therefore, the failure rate of downloading and uploading of the large files can be greatly reduced.

Description

The method and system of upload and download file
Technical field
The invention belongs to file service field, be specifically related to a kind of method and system of upload and download file.
Background technology
In general download and upload file technology, some technology from the direct file reading of disk server, thus are downloaded or upload file, make speed of download and uploading speed so slowly; Although the node address closest to user can be supplied to user by CDN server, when visit capacity is many, still there is underloaded shortcoming in independent CDN server; The network hotspot resource that other independent server does not have cache user often to download while being not enough to bear many visit capacities yet, makes the download of next time and uploads still speed very slow; In addition, existing upload and download method, be not all support that breakpoint is downloaded and uploads, jumbo file is once downloaded or uploads unsuccessful, next time must again be downloaded and upload, waste user time.
Summary of the invention
The object of the invention is to, provide a kind of upload and download method and system, can file fast required for upload and download client.
To achieve these goals, the invention provides a kind of method of download file, comprising:
Client sends download request, the corresponding request path of described download request;
CDN server receives described download request, and judges whether the downloading contents that buffer memory and described download request require, if buffer memory, then this content is turned back to client, if do not have buffer memory, then described download request is sent to IIS Web server;
Described IIS Web server receives the described download request that described CDN server sends, and described download request is resolved, judge whether described IIS Web server has existed the buffer memory of described download request, if exist, then direct corresponding for described download request cache contents is returned client; If do not exist, then resolve the parameter value in described request path further, obtain magnetic disc ID in file path, and described magnetic disc ID is sent to database server;
Described database server receives the described magnetic disc ID that described IIS Web server sends, search database and whether comprise the magnetic disc shares path with described magnetic disc ID with mapping relations, if, then return to described magnetic disc shares path, described magnetic disc shares path resolved again by IIS Web server, obtain the concrete path request of file, and send it to disk server; If not, then send this file to client and there is not message;
Described disk server receives the concrete path request of file that described IIS Web server sends, and whether exist according to this file of the concrete path searching of described file, if so, then return this file corresponding content to client, if not, then backspace file does not exist message.
Preferably, wherein, described database server receives the described magnetic disc ID that described IIS Web server sends, first at Redis data cached library lookup, buffer memory and described magnetic disc ID have the magnetic disc shares path of mapping relations, if so, then described magnetic disc shares path is turned back to IIS Web server, it resolves this magnetic disc shares path again, obtain the concrete path request of file, send it to disk server and carry out file download operation;
If there is no magnetic disc ID corresponding data in described Redis cache database, then inquire about SqlServer relational database and whether comprise the magnetic disc shares path with described magnetic disc ID with mapping relations, if, then described magnetic disc shares path is turned back to IIS Web server, it resolves this magnetic disc shares path again, obtain the concrete path request of file, send it to disk server and carry out file download operation; If not, then send this file to client and there is not message;
If all do not find the magnetic disc shares path with described magnetic disc ID with mapping relations in described Redis cache database and described SqlServer relational database, then send this file to described client and there is not message.
Wherein, described down operation supports that breakpoint is downloaded.
Preferably, wherein, IIS Web server is divided into polytype file server according to business, its domain name addresses corresponding different respectively, described download request obtains corresponding IP by domain name mapping, this IP maps domain name address, then described download request is sent to the file server of corresponding domain name addresses;
Described file server is resolved described download request, judges whether file server internal memory has existed the buffer memory of described download request, if so, then direct corresponding for download request cache contents is returned client; If not, then further analysis request path parameter value, obtains magnetic disc ID in file path, and described magnetic disc ID is sent to described database server.
A kind of file download system, comprising:
Client, it is for sending download request;
CDN server, it is for receiving described download request, and judges whether the downloading contents that buffer memory and described download request require, if buffer memory, then this content is turned back to client, if do not have buffer memory, then described download request is sent to IIS Web server;
Described IIS Web server connects, its described download request sent for receiving described CDN server, and described download request is resolved, judge whether described IIS Web server has existed the buffer memory of described download request, if exist, then direct corresponding for described download request cache contents is returned client; If do not exist, then resolve the parameter value in described request path further, obtain magnetic disc ID in file path, and described magnetic disc ID is sent to database server;
Described database server, its described magnetic disc ID sent for receiving described IIS Web server, search database and whether comprise the magnetic disc shares path with described magnetic disc ID with mapping relations, if, then return to described magnetic disc shares path, described magnetic disc shares path resolved again by IIS Web server, obtains the concrete path request of file, and sends it to disk server; If not, then send this file to client and there is not message;
Described disk server, whether its concrete path request of file sent for receiving described IIS Web server, exist according to this file of the concrete path searching of described file, if, then return this file corresponding content to client, if not, then there is not message in backspace file.
Preferably, wherein, described database server includes the data cached and SqlServer relational database of Redis;
Wherein, described database server receives the described magnetic disc ID that described IIS Web server sends, first at Redis data cached library lookup, buffer memory and described magnetic disc ID have the magnetic disc shares path of mapping relations, if, then described magnetic disc shares path is turned back to IIS Web server, it resolves this magnetic disc shares path again, obtains the concrete path request of file, sends it to disk server and carries out file download operation;
If there is no magnetic disc ID corresponding data in described Redis cache database, then inquire about SqlServer relational database and whether comprise the magnetic disc shares path with described magnetic disc ID with mapping relations, if, then described magnetic disc shares path is turned back to IIS Web server, it resolves this magnetic disc shares path again, obtain the concrete path request of file, send it to disk server and carry out file download operation; If not, then send this file to client and there is not message;
If all do not find the magnetic disc shares path with described magnetic disc ID with mapping relations in described Redis cache database and described SqlServer relational database, then send this file to described client and there is not message;
Wherein, described down operation supports that breakpoint is downloaded.
Preferably, wherein, also comprise:
First checkout gear, whether it normally runs for monitoring described IIS Web server;
Second detection device, whether it normally runs for monitoring described database server;
Multiple file server, it is the file server that IIS Web server separates according to business service, its domain name addresses corresponding different respectively, described download request obtains corresponding IP by domain name mapping, this IP maps domain name address, then described download request is sent to the file server of corresponding domain name addresses;
Described file server is resolved described download request, judges whether file server internal memory has existed the buffer memory of described download request, if so, then direct corresponding for download request cache contents is returned client; If not, then further analysis request path parameter value, obtains magnetic disc ID in file path, and described magnetic disc ID is sent to described database server.
A method for upload file, comprising:
Client sends upload request;
IIS Web server receives described upload request, and described upload request submits upload file relevant information to, and whether IIS server meets agreement to relevant information analysis judgment, if not, then returns; If so, inquiry request is then sent to database server;
Described database server receives the inquiry request that described IIS Web server sends, if not specifying in advance, then search the magnetic disc ID the write collection comprised in described database server, the magnetic disc shares path that therefrom random selecting magnetic disc ID is corresponding is back to IIS Web server; If specify magnetic disc ID in advance, then search described database server and whether there is the magnetic disc shares path with described magnetic disc ID with mapping relations, if not, then sending this file to client cannot upload message, if, then shared disk path corresponding for this magnetic disc ID is returned to IIS Web server, IIS Web server sends write request to disk server after obtaining magnetic disc shares path;
Described disk server receives write request, completes file write operations, and backspace file path, to IIS server, has been uploaded;
Preferably, wherein, described information upload comprises filename, file content, the file whether information such as breakpoint transmission, files passe original position;
Upload request also uploads the magnetic disc ID of path parameter specified file write in advance by specified file;
Wherein, described database server receives the inquiry request that described IIS Web server sends, dish request can be write if described inquiry request is inquiry, first whether comprise can write disk at the data cached library lookup of Redis, if so, the magnetic disc shares path that then random selecting one is corresponding returns IIS Web server; Whether if not, then inquire about SqlServer relational database and comprise and can write disk, if do not comprised, then backspace file cannot upload message, if comprised, then the magnetic disc shares path that random selecting one is corresponding from corresponding result set returns IIS Web server; IIS Web server sends write request to disk server after obtaining magnetic disc shares path; It receives write request, completes file write operations, and backspace file path, to IIS server, has been uploaded;
Wherein, support breakpoint transmission is uploaded described in.
If described inquiry request is inquiry designated disk ID request, first the magnetic disc shares path having mapping relations with described magnetic disc ID whether is there is at the data cached library inquiry of Redis, if, then this magnetic disc shares path is returned IIS Web server, if not, then at SqlServer database lookup, if exist at described SqlServer database, then this magnetic disc shares path is returned IIS Web server; IIS Web server obtains magnetic disc shares path and sends writing in files request to disk server; IIS Web server sends write request to disk server after obtaining magnetic disc shares path; It receives write request, completes file write operations, and backspace file path, to IIS server, has been uploaded;
Wherein, support breakpoint transmission is uploaded described in.
If all do not find in described Redis cache database and described SqlServer database and the magnetic disc shares path having described magnetic disc ID to have mapping relations, then sending this file to client cannot upload message.
A system for upload file, comprising:
Client, it is for sending upload request;
IIS Web server, it is for receiving described upload request, and described upload request submits upload file relevant information to, and whether IIS server meets agreement to relevant information analysis judgment, if not, then returns; If so, inquiry request is then sent to database server;
Described database server, it receives the inquiry request that described IIS Web server sends, if not specifying in advance, then search the magnetic disc ID the write collection comprised in described database server, the magnetic disc shares path that therefrom random selecting magnetic disc ID is corresponding is back to IIS Web server; If specify magnetic disc ID in advance, then search described database server and whether there is the magnetic disc shares path with described magnetic disc ID with mapping relations, if not, then sending this file to client cannot upload message, if, then shared disk path corresponding for this magnetic disc ID is returned to IIS Web server, IIS Web server sends write request to disk server after obtaining magnetic disc shares path;
Described disk server, it receives write request, completes file write operations, and backspace file path, to IIS server, has been uploaded;
Preferably, wherein, also comprise:
First checkout gear, whether it normally runs for monitoring described IIS Web server;
Second detection device, whether it normally runs for monitoring described database server;
Described database comprises Redis cache database and SqlServer relational database;
Wherein, described database server receives the inquiry request that described IIS Web server sends, dish request can be write if described inquiry request is inquiry, first whether comprise can write disk at the data cached library lookup of Redis, if so, the magnetic disc shares path that then random selecting one is corresponding returns IIS Web server; Whether if not, then inquire about SqlServer relational database and comprise and can write disk, if not, then backspace file cannot upload message, and the magnetic disc shares path that if so, then random selecting one is corresponding from corresponding result set returns IIS Web server; IIS Web server sends write request to disk server after obtaining magnetic disc shares path; It receives write request, completes file write operations, and backspace file path, to IIS server, has been uploaded;
Wherein, support breakpoint transmission is uploaded described in.
If described inquiry request is inquiry designated disk ID request, first the magnetic disc shares path having mapping relations with described magnetic disc ID whether is there is at the data cached library inquiry of Redis, if, then this magnetic disc shares path is returned IIS Web server, if not, then at SqlServer database lookup, if exist at described SqlServer database, then this magnetic disc shares path is returned IIS Web server; IIS Web server obtains magnetic disc shares path and sends writing in files request to disk server; IIS Web server sends write request to disk server after obtaining magnetic disc shares path; It receives write request, completes file write operations, and backspace file path, to IIS server, has been uploaded;
Wherein, support breakpoint transmission is uploaded described in.
If all do not find in described Redis cache database and described SqlServer database and the magnetic disc shares path having described magnetic disc ID to have mapping relations, then sending this file to client cannot upload message.
Beneficial effect of the present invention
1, CDN server provided by the invention, speeds the speed downloaded and upload;
2, provided by the invention according to the distributed multiple kind of document of type of service, and the multiple storage server of load, performance better, more flexible, enhance service stability;
3, the first checkout gear provided by the invention and second detection device, ensure that the stability of service operation state;
4, Redis cache database provided by the invention, the download made and the speed uploaded faster;
5, shared disk reading manner provided by the invention is flexible, and disk server autgmentability is better, and the special user right of local area network (LAN) controls safer;
6, the present invention adopts CDN server, IIS Web server, database server and disk server together provide to be downloaded and uploads, and makes the speed downloading and upload faster.
Accompanying drawing explanation
Fig. 1 is the Organization Chart of upload and download method and system of the present invention;
Embodiment
Below in conjunction with accompanying drawing, the present invention is described in further detail, can implement according to this with reference to specification word to make those skilled in the art.
As shown in Figure 1, solid line is wherein the method for download request, and dotted line is the method for upload request.
Client/Application is client;
Server1, Server2 etc. are the citing of multiple storage server;
Fielserver (image-text), APPFielserver (application class), MVPFielserver (multimedia class), BTPFielserver (commerce and trade class), CCPFielserver (communication class) are the kind of document pressing service distribution;
Server monitoring is the first checkout gear, and Redis monitoring is second detection device;
Client sends download request, the corresponding request path of described download request;
CDN server receives described download request, and judges whether the downloading contents that buffer memory and described download request require, if buffer memory, then this content is turned back to client, if do not have buffer memory, then described download request is sent to IIS Web server;
Described IIS Web server receives the described download request that described CDN server sends, and described download request is resolved, judge whether described IIS Web server has existed the buffer memory of described download request, if exist, then direct corresponding for described download request cache contents is returned client; If do not exist, then resolve the parameter value in described request path further, obtain magnetic disc ID in file path, and described magnetic disc ID is sent to database server;
Described database server receives the described magnetic disc ID that described IIS Web server sends, search database and whether comprise the magnetic disc shares path with described magnetic disc ID with mapping relations, if, then return to described magnetic disc shares path, described magnetic disc shares path resolved again by IIS Web server, obtain the concrete path request of file, and send it to disk server; If not, then send this file to client and there is not message;
Described disk server receives the concrete path request of file that described IIS Web server sends, and whether exist according to this file of the concrete path searching of described file, if so, then return this file corresponding content to client, if not, then backspace file does not exist message.
For ensureing that secure file system creates special sharing users and creates password, dish is shared in read-write all to be needed to provide correct user name and password.Because file is more, for convenience of management, file directory is produced by certain rule, comprises by date (as 2014112618 during the date) and name (as img/apk) two class by file type at present.
CDN is the distributed content delivery network of one built over data networks.The effect of CDN adopts streaming media server Clustering, overcomes the shortcoming of one-of-a-kind system output bandwidth and concurrent capability deficiency, can the concurrent flow amount supported of significant increase system, the harmful effect reducing or avoid single point failure to bring.
The present invention allows download request first by CDN server, and CDN utilizes GSLB technology to point to the access of user from the nearest streaming media server working properly of user, is directly responded the request of user by streaming media server.If there is no the content that user will access in server, then provide download by underlying services device provided by the invention, so in layer search, directly need not search in the various file of disk server, speed of download can be improved widely.
An embodiment, on the basis of above-mentioned situation,
Described database server receives the described magnetic disc ID that described IIS Web server sends, first at Redis data cached library lookup, buffer memory and described magnetic disc ID have the magnetic disc shares path of mapping relations, if, then described magnetic disc shares path is turned back to IIS Web server, it resolves this magnetic disc shares path again, obtain the concrete path request of file, send it to disk server and carry out file download operation;
If there is no magnetic disc ID corresponding data in described Redis cache database, then inquire about SqlServer relational database and whether comprise the magnetic disc shares path with described magnetic disc ID with mapping relations, if, then described magnetic disc shares path is turned back to IIS Web server, it resolves this magnetic disc shares path again, obtain the concrete path request of file, send it to disk server and carry out file download operation; If not, then send this file to client and there is not message;
If all do not find the magnetic disc shares path with described magnetic disc ID with mapping relations in described Redis cache database and described SqlServer relational database, then send this file to described client and there is not message.
Wherein, described down operation supports that breakpoint is downloaded.
Redis is a key-value storage system.It supports that the value type stored is relatively more, comprises string (character string), list (chained list), set (set), zset (sorted set--ordered set) and hash (Hash type).These data types are all supported push/pop, add/remove and are got common factor union and difference set and abundanter operation, and these operations are all atomicities.On this basis, Redis supports the sequence of various different modes.In order to guaranteed efficiency, data are all be buffered in internal memory.Redis periodically the data write disk upgraded or the log file that retouching operation write is added, and can achieve master-slave (principal and subordinate) synchronously on this basis.
Redis is a high performance key-value database.The appearance of Redis, largely compensate for the deficiency that this kind of key/value of memcached stores, can play good supplementary function in part occasion to relational database.It provide Java, the clients such as C/C++, C#, PHP, JavaScript, Perl, Object-C, Python, Ruby, Erlang, use easily.
Redis supports master-slave synchronisation.Data can synchronous from server from master server to any amount, can be other master servers from server of association from server.This makes Redis can perform individual layer tree copying.Deposit consciously or unconsciously can carry out write operation to data.Owing to fully achieving publish/subscribe mechanism, make from database anywhere synchronization tree time, a channel can be subscribed to and receive the complete news release record of master server.Synchronously to the extensibility of read operation and data redundancy helpful.
In addition, download and support that breakpoint is downloaded, namely when file is large especially, greatly can reduce large files failed download rate because network reason etc. affects large files segmentation download;
Another embodiment, on the basis of above-described embodiment, described IIS Web server is divided into polytype file server according to business, its domain name addresses corresponding different respectively, described download request obtains corresponding IP by domain name mapping, this IP maps domain name address, then described download request is sent to the file server of corresponding domain name addresses;
Described file server is resolved described download request, judges whether file server internal memory has existed the buffer memory of described download request, if so, then direct corresponding for download request cache contents is returned client; If not, then further analysis request path parameter value, obtains magnetic disc ID in file path, and described magnetic disc ID is sent to described database server.
For supporting that each service scripts service of larger visit capacity adopts again multiple servers to carry out load, can increase the visit capacity of described IIS Web server, the speed of download made is faster.
A kind of file download system, comprising:
Client, it is for sending download request;
CDN server, it is for receiving described download request, and judges whether the downloading contents that buffer memory and described download request require, if buffer memory, then this content is turned back to client, if do not have buffer memory, then described download request is sent to IIS Web server;
Described IIS Web server connects, its described download request sent for receiving described CDN server, and described download request is resolved, judge whether described IIS Web server has existed the buffer memory of described download request, if exist, then direct corresponding for described download request cache contents is returned client; If do not exist, then resolve the parameter value in described request path further, obtain magnetic disc ID in file path, and described magnetic disc ID is sent to database server;
Described database server, its described magnetic disc ID sent for receiving described IIS Web server, search database and whether comprise the magnetic disc shares path with described magnetic disc ID with mapping relations, if, then return to described magnetic disc shares path, described magnetic disc shares path resolved again by IIS Web server, obtains the concrete path request of file, and sends it to disk server; If not, then send this file to client and there is not message;
Described disk server, whether its concrete path request of file sent for receiving described IIS Web server, exist according to this file of the concrete path searching of described file, if, then return this file corresponding content to client, if not, then there is not message in backspace file.
For ensureing that secure file system creates special sharing users and creates password, dish is shared in read-write all to be needed to provide correct user name and password.Because file is more, for convenience of management, file directory is produced by certain rule, comprises by date (as 2014112618 during the date) and name (as img/apk) two class by file type at present.
An embodiment, on the basis of above-mentioned situation, described database server includes the data cached and SqlServer relational database of Redis;
Wherein, described database server receives the described magnetic disc ID that described IIS Web server sends, first at Redis data cached library lookup, buffer memory and described magnetic disc ID have the magnetic disc shares path of mapping relations, if, then described magnetic disc shares path is turned back to IIS Web server, it resolves this magnetic disc shares path again, obtains the concrete path request of file, sends it to disk server and carries out file download operation;
If there is no magnetic disc ID corresponding data in described Redis cache database, then inquire about SqlServer relational database and whether comprise the magnetic disc shares path with described magnetic disc ID with mapping relations, if, then described magnetic disc shares path is turned back to IIS Web server, it resolves this magnetic disc shares path again, obtain the concrete path request of file, send it to disk server and carry out file download operation; If not, then send this file to client and there is not message;
If all do not find the magnetic disc shares path with described magnetic disc ID with mapping relations in described Redis cache database and described SqlServer relational database, then send this file to described client and there is not message;
Wherein, described down operation supports that breakpoint is downloaded;
Download and support that breakpoint is downloaded, namely when file is large especially, greatly can reduce large files failed download rate because network reason etc. affects large files segmentation download;
Another embodiment, on the basis of above-described embodiment, also comprises:
First checkout gear, whether it normally runs for monitoring described IIS Web server;
Second detection device, whether it normally runs for monitoring described database server;
Multiple file server, it is the file server that IIS Web server separates according to business service, its domain name addresses corresponding different respectively, described download request obtains corresponding IP by domain name mapping, this IP maps domain name address, then described download request is sent to the file server of corresponding domain name addresses;
Described file server is resolved described download request, judges whether file server internal memory has existed the buffer memory of described download request, if so, then direct corresponding for download request cache contents is returned client; If not, then further analysis request path parameter value, obtains magnetic disc ID in file path, and described magnetic disc ID is sent to described database server.
A method for upload file, comprising:
Client sends upload request;
IIS Web server receives described upload request, and described upload request submits upload file relevant information to, and whether IIS server meets agreement to relevant information analysis judgment, if not, then returns; If so, inquiry request is then sent to database server;
Described database server receives the inquiry request that described IIS Web server sends, if not specifying in advance, then search the magnetic disc ID the write collection comprised in described database server, the magnetic disc shares path that therefrom random selecting magnetic disc ID is corresponding is back to IIS Web server; If specify magnetic disc ID in advance, then search described database server and whether there is the magnetic disc shares path with described magnetic disc ID with mapping relations, if not, then sending this file to client cannot upload message, if, then shared disk path corresponding for this magnetic disc ID is returned to IIS Web server, IIS Web server sends write request to disk server after obtaining magnetic disc shares path;
Described disk server receives write request, completes file write operations, and backspace file path, to IIS server, has been uploaded;
Another embodiment, on the basis of above-described embodiment, described information upload comprises filename, file content, the file whether information such as breakpoint transmission, files passe original position;
Upload request also uploads the magnetic disc ID of path parameter specified file write in advance by specified file;
Wherein, described database server receives the inquiry request that described IIS Web server sends, dish request can be write if described inquiry request is inquiry, first whether comprise can write disk at the data cached library lookup of Redis, if so, the magnetic disc shares path that then random selecting one is corresponding returns IIS Web server; Whether if not, then inquire about SqlServer relational database and comprise and can write disk, if do not comprised, then backspace file cannot upload message, if comprised, then the magnetic disc shares path that random selecting one is corresponding from corresponding result set returns IIS Web server; IIS Web server sends write request to disk server after obtaining magnetic disc shares path; It receives write request, completes file write operations, and backspace file path, to IIS server, has been uploaded;
Wherein, support breakpoint transmission is uploaded described in.
If described inquiry request is inquiry designated disk ID request, first the magnetic disc shares path having mapping relations with described magnetic disc ID whether is there is at the data cached library inquiry of Redis, if, then this magnetic disc shares path is returned IIS Web server, if not, then at SqlServer database lookup, if exist at described SqlServer database, then this magnetic disc shares path is returned IIS Web server; IIS Web server obtains magnetic disc shares path and sends writing in files request to disk server; IIS Web server sends write request to disk server after obtaining magnetic disc shares path; It receives write request, completes file write operations, and backspace file path, to IIS server, has been uploaded;
Wherein, support breakpoint transmission is uploaded described in.
If all do not find in described Redis cache database and described SqlServer database and the magnetic disc shares path having described magnetic disc ID to have mapping relations, then sending this file to client cannot upload message.
Breakpoint transmission is supported in upload file, ensures large files segmentation write disk.
A system for upload file, comprising:
Client, it is for sending upload request;
IIS Web server, it is for receiving described upload request, and described upload request submits upload file relevant information to, and whether IIS server meets agreement to relevant information analysis judgment, if not, then returns; If so, inquiry request is then sent to database server;
Described database server, it receives the inquiry request that described IIS Web server sends, if not specifying in advance, then search the magnetic disc ID the write collection comprised in described database server, the magnetic disc shares path that therefrom random selecting magnetic disc ID is corresponding is back to IIS Web server; If specify magnetic disc ID in advance, then search described database server and whether there is the magnetic disc shares path with described magnetic disc ID with mapping relations, if not, then sending this file to client cannot upload message, if, then shared disk path corresponding for this magnetic disc ID is returned to IIS Web server, IIS Web server sends write request to disk server after obtaining magnetic disc shares path;
Described disk server, it receives write request, completes file write operations, and backspace file path, to IIS server, has been uploaded;
For ensureing that secure file system creates special sharing users and creates password, dish is shared in read-write all to be needed to provide correct user name and password.Because file is more, for convenience of management, file directory is produced by certain rule, comprises by date (as 2014112618 during the date) and name (as img/apk) two class by file type at present.
Another embodiment, on the basis of above-described embodiment, the system of described upload file, also comprises:
First checkout gear, whether it normally runs for monitoring described IIS Web server;
Second detection device, whether it normally runs for monitoring described database server;
Described database comprises Redis cache database and SqlServer relational database;
Wherein, described database server receives the inquiry request that described IIS Web server sends, dish request can be write if described inquiry request is inquiry, first whether comprise can write disk at the data cached library lookup of Redis, if so, the magnetic disc shares path that then random selecting one is corresponding returns IIS Web server; Whether if not, then inquire about SqlServer relational database and comprise and can write disk, if not, then backspace file cannot upload message, and the magnetic disc shares path that if so, then random selecting one is corresponding from corresponding result set returns IIS Web server; IIS Web server sends write request to disk server after obtaining magnetic disc shares path; It receives write request, completes file write operations, and backspace file path, to IIS server, has been uploaded;
Wherein, support breakpoint transmission is uploaded described in.
If described inquiry request is inquiry designated disk ID request, first the magnetic disc shares path having mapping relations with described magnetic disc ID whether is there is at the data cached library inquiry of Redis, if, then this magnetic disc shares path is returned IIS Web server, if not, then at SqlServer database lookup, if exist at described SqlServer database, then this magnetic disc shares path is returned IIS Web server; IIS Web server obtains magnetic disc shares path and sends writing in files request to disk server; IIS Web server sends write request to disk server after obtaining magnetic disc shares path; It receives write request, completes file write operations, and backspace file path, to IIS server, has been uploaded;
Wherein, support breakpoint transmission is uploaded described in.
If all do not find in described Redis cache database and described SqlServer database and the magnetic disc shares path having described magnetic disc ID to have mapping relations, then sending this file to client cannot upload message.
Wherein, described first checkout gear analyzes IIS server log, and in daily record, abnormal information (the HTTP mistakes of 4 or 5 classes) can be sent out mail alarm related personnel and processes in time.The monitoring of service operation state more strengthens stability and ensures.
Wherein, whether described second detection device detects cache database and normally runs, if be closed, and can autoboot.
For ensureing that secure file system creates special sharing users and creates password, dish is shared in read-write all to be needed to provide correct user name and password.Because file is more, for convenience of management, file directory is produced by certain rule, comprises by date (as 2014112618 during the date) and name (as img/apk) two class by file type at present.
Wherein, picture file, picture display is exactly a download request; Audio-video document, broadcasting is exactly download request.
Although embodiment of the present invention are open as above, but it is not restricted to listed in specification and execution mode utilization, it can be applied to various applicable the field of the invention completely, for those skilled in the art, can easily realize other amendment, therefore do not deviating under the universal that claim and equivalency range limit, the present invention is not limited to specific details and illustrates here and the legend described.

Claims (10)

1. a method for download file, comprising:
Client sends download request; The corresponding request path of described download request;
CDN server receives described download request, and judges whether the downloading contents that buffer memory and described download request require, if buffer memory, then this content is turned back to client, if do not have buffer memory, then described download request is sent to IIS Web server;
Described IIS Web server receives the described download request that described CDN server sends, and described download request is resolved, judge whether described IIS Web server has existed the buffer memory of described download request, if exist, then direct corresponding for described download request cache contents is returned client; If do not exist, then resolve the parameter value in described request path further, obtain magnetic disc ID in file path, and described magnetic disc ID is sent to database server;
Described database server receives the described magnetic disc ID that described IIS Web server sends, search database and whether comprise the magnetic disc shares path with described magnetic disc ID with mapping relations, if, then return to described magnetic disc shares path, described magnetic disc shares path resolved again by IIS Web server, obtain the concrete path request of file, and send it to disk server; If not, then send this file to client and there is not message;
Described disk server receives the concrete path request of file that described IIS Web server sends, and whether exist according to this file of the concrete path searching of described file, if so, then return this file corresponding content to client, if not, then backspace file does not exist message.
2. the method for claim 1, wherein, described database server receives the described magnetic disc ID that described IIS Web server sends, first at Redis data cached library lookup, buffer memory and described magnetic disc ID have the magnetic disc shares path of mapping relations, if so, then described magnetic disc shares path is turned back to IIS Web server, it resolves this magnetic disc shares path again, obtain the concrete path request of file, send it to disk server and carry out file download operation;
If there is no magnetic disc ID corresponding data in described Redis cache database, then inquire about SqlServer relational database and whether comprise the magnetic disc shares path with described magnetic disc ID with mapping relations, if, then described magnetic disc shares path is turned back to IIS Web server, it resolves this magnetic disc shares path again, obtain the concrete path request of file, send it to disk server and carry out file download operation; If not, then send this file to client and there is not message;
If all do not find the magnetic disc shares path with described magnetic disc ID with mapping relations in described Redis cache database and described SqlServer relational database, then send this file to described client and there is not message.
Wherein, described down operation supports that breakpoint is downloaded.
3. the method for claim 1, wherein, IIS Web server is divided into polytype file server according to business, its domain name addresses corresponding different respectively, described download request obtains corresponding IP by domain name mapping, this IP maps domain name address, then described download request is sent to the file server of corresponding domain name addresses;
Described file server is resolved described download request, judges whether file server internal memory has existed the buffer memory of described download request, if so, then direct corresponding for download request cache contents is returned client; If not, then further analysis request path parameter value, obtains magnetic disc ID in file path, and described magnetic disc ID is sent to described database server.
4. a file download system, comprising:
Client, it is for sending download request;
CDN server, it is for receiving described download request, and judges whether the downloading contents that buffer memory and described download request require, if buffer memory, then this content is turned back to client, if do not have buffer memory, then described download request is sent to IIS Web server;
Described IIS Web server connects, its described download request sent for receiving described CDN server, and described download request is resolved, judge whether described IIS Web server has existed the buffer memory of described download request, if exist, then direct corresponding for described download request cache contents is returned client; If do not exist, then resolve the parameter value in described request path further, obtain magnetic disc ID in file path, and described magnetic disc ID is sent to database server;
Described database server, its described magnetic disc ID sent for receiving described IIS Web server, search database and whether comprise the magnetic disc shares path with described magnetic disc ID with mapping relations, if, then return to described magnetic disc shares path, described magnetic disc shares path resolved again by IIS Web server, obtains the concrete path request of file, and sends it to disk server; If not, then send this file to client and there is not message;
Described disk server, whether its concrete path request of file sent for receiving described IIS Web server, exist according to this file of the concrete path searching of described file, if, then return this file corresponding content to client, if not, then there is not message in backspace file.
5. file download system as claimed in claim 4, wherein, described database server includes the data cached and SqlServer relational database of Redis;
Wherein, described database server receives the described magnetic disc ID that described IIS Web server sends, first at Redis data cached library lookup, buffer memory and described magnetic disc ID have the magnetic disc shares path of mapping relations, if, then described magnetic disc shares path is turned back to IIS Web server, it resolves this magnetic disc shares path again, obtains the concrete path request of file, sends it to disk server and carries out file download operation;
If there is no magnetic disc ID corresponding data in described Redis cache database, then inquire about SqlServer relational database and whether comprise the magnetic disc shares path with described magnetic disc ID with mapping relations, if, then described magnetic disc shares path is turned back to IIS Web server, it resolves this magnetic disc shares path again, obtain the concrete path request of file, send it to disk server and carry out file download operation; If not, then send this file to client and there is not message;
If all do not find the magnetic disc shares path with described magnetic disc ID with mapping relations in described Redis cache database and described SqlServer relational database, then send this file to described client and there is not message;
Wherein, described down operation supports that breakpoint is downloaded.
6. file download system as claimed in claim 4, wherein, also comprises:
First checkout gear, whether it normally runs for monitoring described IIS Web server;
Second detection device, whether it normally runs for monitoring described database server;
Multiple file server, it is the file server that IIS Web server separates according to business service, its domain name addresses corresponding different respectively, described download request obtains corresponding IP by domain name mapping, this IP maps domain name address, then described download request is sent to the file server of corresponding domain name addresses;
Described file server is resolved described download request, judges whether file server internal memory has existed the buffer memory of described download request, if so, then direct corresponding for download request cache contents is returned client; If not, then further analysis request path parameter value, obtains magnetic disc ID in file path, and described magnetic disc ID is sent to described database server.
7. a method for upload file, comprising:
Client sends upload request;
IIS Web server receives described upload request, and described upload request submits upload file relevant information to, and whether IIS server meets agreement to relevant information analysis judgment, if not, then returns; If so, inquiry request is then sent to database server;
Described database server receives the inquiry request that described IIS Web server sends, if not specifying in advance, then search the magnetic disc ID the write collection comprised in described database server, the magnetic disc shares path that therefrom random selecting magnetic disc ID is corresponding is back to IIS Web server; If specify magnetic disc ID in advance, then search described database server and whether there is the magnetic disc shares path with described magnetic disc ID with mapping relations, if not, then sending this file to client cannot upload message, if, then shared disk path corresponding for this magnetic disc ID is returned to IIS Web server, IIS Web server sends write request to disk server after obtaining magnetic disc shares path;
Described disk server receives write request, completes file write operations, and backspace file path, to IIS server, has been uploaded.
8. as claimed in claim 7 method of planting upload file, wherein, described information upload comprises filename, file content, the file whether information such as breakpoint transmission, files passe original position;
Upload request also uploads the magnetic disc ID of path parameter specified file write in advance by specified file;
Wherein, described database server receives the inquiry request that described IIS Web server sends, dish request can be write if described inquiry request is inquiry, first whether comprise can write disk at the data cached library lookup of Redis, if so, the magnetic disc shares path that then random selecting one is corresponding returns IIS Web server; Whether if not, then inquire about SqlServer relational database and comprise and can write disk, if do not comprised, then backspace file cannot upload message, if comprised, then the magnetic disc shares path that random selecting one is corresponding from corresponding result set returns IIS Web server; IIS Web server sends write request to disk server after obtaining magnetic disc shares path; It receives write request, completes file write operations, and backspace file path, to IIS server, has been uploaded;
Wherein, support breakpoint transmission is uploaded described in.
If described inquiry request is inquiry designated disk ID request, first the magnetic disc shares path having mapping relations with described magnetic disc ID whether is there is at the data cached library inquiry of Redis, if, then this magnetic disc shares path is returned IIS Web server, if not, then at SqlServer database lookup, if exist at described SqlServer database, then this magnetic disc shares path is returned IIS Web server; IIS Web server obtains magnetic disc shares path and sends writing in files request to disk server; IIS Web server sends write request to disk server after obtaining magnetic disc shares path; It receives write request, completes file write operations, and backspace file path, to IIS server, has been uploaded;
Wherein, support breakpoint transmission is uploaded described in.
If all do not find in described Redis cache database and described SqlServer database and the magnetic disc shares path having described magnetic disc ID to have mapping relations, then sending this file to client cannot upload message.
9. a system for upload file, comprising:
Client, it is for sending upload request;
IIS Web server, it is for receiving described upload request, and described upload request submits upload file relevant information to, and whether IIS server meets agreement to relevant information analysis judgment, if not, then returns; If so, inquiry request is then sent to database server;
Described database server, it receives the inquiry request that described IIS Web server sends, if not specifying in advance, then search the magnetic disc ID the write collection comprised in described database server, the magnetic disc shares path that therefrom random selecting magnetic disc ID is corresponding is back to IIS Web server; If specify magnetic disc ID in advance, then search described database server and whether there is the magnetic disc shares path with described magnetic disc ID with mapping relations, if not, then sending this file to client cannot upload message, if, then shared disk path corresponding for this magnetic disc ID is returned to IIS Web server, IIS Web server sends write request to disk server after obtaining magnetic disc shares path;
Described disk server, it receives write request, completes file write operations, and backspace file path, to IIS server, has been uploaded.
10. the system of upload file as claimed in claim 9, wherein, also comprises:
First checkout gear, whether it normally runs for monitoring described IIS Web server;
Second detection device, whether it normally runs for monitoring described database server;
Described database comprises Redis cache database and SqlServer relational database;
Wherein, described database server receives the inquiry request that described IIS Web server sends, dish request can be write if described inquiry request is inquiry, first whether comprise can write disk at the data cached library lookup of Redis, if so, the magnetic disc shares path that then random selecting one is corresponding returns IIS Web server; Whether if not, then inquire about SqlServer relational database and comprise and can write disk, if not, then backspace file cannot upload message, and the magnetic disc shares path that if so, then random selecting one is corresponding from corresponding result set returns IIS Web server; IIS Web server sends write request to disk server after obtaining magnetic disc shares path; It receives write request, completes file write operations, and backspace file path, to IIS server, has been uploaded;
Wherein, support breakpoint transmission is uploaded described in.
If described inquiry request is inquiry designated disk ID request, first the magnetic disc shares path having mapping relations with described magnetic disc ID whether is there is at the data cached library inquiry of Redis, if, then this magnetic disc shares path is returned IIS Web server, if not, then at SqlServer database lookup, if exist at described SqlServer database, then this magnetic disc shares path is returned IIS Web server; IIS Web server obtains magnetic disc shares path and sends writing in files request to disk server; IIS Web server sends write request to disk server after obtaining magnetic disc shares path; It receives write request, completes file write operations, and backspace file path, to IIS server, has been uploaded;
Wherein, support breakpoint transmission is uploaded described in.
If all do not find in described Redis cache database and described SqlServer database and the magnetic disc shares path having described magnetic disc ID to have mapping relations, then sending this file to client cannot upload message.
CN201510057145.XA 2015-02-03 2015-02-03 Upload and download the method and system of file Active CN104601724B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201510057145.XA CN104601724B (en) 2015-02-03 2015-02-03 Upload and download the method and system of file

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201510057145.XA CN104601724B (en) 2015-02-03 2015-02-03 Upload and download the method and system of file

Publications (2)

Publication Number Publication Date
CN104601724A true CN104601724A (en) 2015-05-06
CN104601724B CN104601724B (en) 2018-01-23

Family

ID=53127217

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201510057145.XA Active CN104601724B (en) 2015-02-03 2015-02-03 Upload and download the method and system of file

Country Status (1)

Country Link
CN (1) CN104601724B (en)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105763604A (en) * 2016-02-04 2016-07-13 四川长虹电器股份有限公司 Lightweight distributed file system and method for recovering original name of downloaded file
CN106067896A (en) * 2016-05-30 2016-11-02 刘华英 File continuous transmission method and device
WO2017097025A1 (en) * 2015-12-09 2017-06-15 上海斐讯数据通信技术有限公司 Samba configuration management method for network device and system
CN107122491A (en) * 2017-05-19 2017-09-01 深圳市优必选科技有限公司 Method for data interaction
CN107278366A (en) * 2017-05-27 2017-10-20 福建联迪商用设备有限公司 A kind of method for down loading and its download system for improving download efficiency
CN109150998A (en) * 2018-08-01 2019-01-04 北京奇虎科技有限公司 Journal file processing system and method based on cloud test platform
CN109889568A (en) * 2018-12-29 2019-06-14 北京城市网邻信息技术有限公司 A kind of data export method, server, client and system
CN111225032A (en) * 2019-12-19 2020-06-02 福建升腾资讯有限公司 Method, system, device and medium for separating application service and file service
CN111427724A (en) * 2020-03-20 2020-07-17 上海圣剑网络科技股份有限公司 Server security stabilization method and architecture thereof
CN112437160A (en) * 2020-11-25 2021-03-02 中国电子科技集团公司第二十九研究所 Method and system for realizing real-time transmission processing of large file based on redis
CN114124925A (en) * 2020-08-25 2022-03-01 华为技术有限公司 Electronic mail synchronization method and electronic equipment

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103078936A (en) * 2012-12-31 2013-05-01 网宿科技股份有限公司 Metadata hierarchical storage method and system for Global file system (GFS)-based distributed file system
EP2458506B1 (en) * 2010-11-30 2013-11-20 Open Text S.A. System and method for managing a cache using file system metadata
CN103986976A (en) * 2014-06-05 2014-08-13 北京赛维安讯科技发展有限公司 Content delivery network (CDN)-based transmission system and method

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2458506B1 (en) * 2010-11-30 2013-11-20 Open Text S.A. System and method for managing a cache using file system metadata
CN103078936A (en) * 2012-12-31 2013-05-01 网宿科技股份有限公司 Metadata hierarchical storage method and system for Global file system (GFS)-based distributed file system
CN103986976A (en) * 2014-06-05 2014-08-13 北京赛维安讯科技发展有限公司 Content delivery network (CDN)-based transmission system and method

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
JIEFOREST: ""StackOverflow的架构及存储,http://www.itpub.net/thread-1880348-1-1.html"", 《ITPUB论坛》 *
MARCO CECCONI: ""The Achitecture of stackoverflow,https://speakerdeck.com/sklivvz/the-architecture-of-stackoverflow-developer-conference-2013"", 《SPEAKERDECK》 *
钟永峰 等: "《Web冲浪指南》", 31 August 2000, 北京工业出版社 *

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017097025A1 (en) * 2015-12-09 2017-06-15 上海斐讯数据通信技术有限公司 Samba configuration management method for network device and system
CN105763604B (en) * 2016-02-04 2019-03-19 四川长虹电器股份有限公司 Lightweight distributed file system and the method for restoring downloading file original name
CN105763604A (en) * 2016-02-04 2016-07-13 四川长虹电器股份有限公司 Lightweight distributed file system and method for recovering original name of downloaded file
CN106067896A (en) * 2016-05-30 2016-11-02 刘华英 File continuous transmission method and device
CN107122491B (en) * 2017-05-19 2020-12-15 深圳市优必选科技有限公司 Method for data interaction
CN107122491A (en) * 2017-05-19 2017-09-01 深圳市优必选科技有限公司 Method for data interaction
CN107278366A (en) * 2017-05-27 2017-10-20 福建联迪商用设备有限公司 A kind of method for down loading and its download system for improving download efficiency
CN109150998A (en) * 2018-08-01 2019-01-04 北京奇虎科技有限公司 Journal file processing system and method based on cloud test platform
CN109889568A (en) * 2018-12-29 2019-06-14 北京城市网邻信息技术有限公司 A kind of data export method, server, client and system
CN109889568B (en) * 2018-12-29 2022-03-29 北京城市网邻信息技术有限公司 Data export method, server and system
CN111225032A (en) * 2019-12-19 2020-06-02 福建升腾资讯有限公司 Method, system, device and medium for separating application service and file service
CN111427724A (en) * 2020-03-20 2020-07-17 上海圣剑网络科技股份有限公司 Server security stabilization method and architecture thereof
CN114124925A (en) * 2020-08-25 2022-03-01 华为技术有限公司 Electronic mail synchronization method and electronic equipment
CN114124925B (en) * 2020-08-25 2023-05-12 华为技术有限公司 E-mail synchronization method and electronic equipment
US12003475B2 (en) 2020-08-25 2024-06-04 Huawei Technologies Co., Ltd. Email synchronization method and electronic device
CN112437160A (en) * 2020-11-25 2021-03-02 中国电子科技集团公司第二十九研究所 Method and system for realizing real-time transmission processing of large file based on redis
CN112437160B (en) * 2020-11-25 2022-06-07 中国电子科技集团公司第二十九研究所 Method and system for realizing real-time transmission processing of large file based on redis

Also Published As

Publication number Publication date
CN104601724B (en) 2018-01-23

Similar Documents

Publication Publication Date Title
CN104601724A (en) Method and system for uploading and downloading file
CN107861686B (en) File storage method, server and computer readable storage medium
US11095602B2 (en) Media streaming system supporting several streaming engines and using content addressing
US10515058B2 (en) Unified file and object data storage
US20180309845A1 (en) Method and system of dispatching requests in a content delivery network
CN106576078B (en) Method and system for routing data streams in cloud storage system
CN108984560B (en) File storage method and device
US20150215405A1 (en) Methods of managing and storing distributed files based on information-centric network
CN101729442B (en) Method and device for realizing content sharing
Sandler et al. Feedtree: Sharing web micronews with peer-to-peer event notification
US8880698B2 (en) Storage of content data in a peer-to-peer network
US10592475B1 (en) Consistent data storage in distributed computing systems
US20060168126A1 (en) Aggregated content listing for ad-hoc peer to peer networks
US8214355B2 (en) Small table: multitenancy for lots of small tables on a cloud database
US20090063507A1 (en) Methods and apparatus for retrieving content
US20080172445A1 (en) Method and System For Increasing Popularity of Content Items Shared Over Peer-to-Peer Networks
CN102882985A (en) File sharing method based on cloud storage
US20110099226A1 (en) Method of requesting for location information of resources on network, user node and server for the same
US9165004B2 (en) Associated content system
US11575773B2 (en) Request processing in a content delivery framework
US9253143B2 (en) Reverse subscriptions
Alimi et al. A survey of in-network storage systems
CN115004665B (en) File sharing method, device and system
CN110347656B (en) Method and device for managing requests in file storage system
KR20070038665A (en) Distributed file system and operating method thereof

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant