在性能方面应该没有问题。
使用async await并不能提供很多改进。这个
FileStreamer
正在利用异步操作访问文件流。
如果坚持使用async await,可以考虑在
Task.Run
让行动返回
Task<HttpResponseMessage>
.
这里真的不需要过早的优化。
例如
public async Task<IHttpActionResult> Get(string filename) {
var filePath = await GetFilePathAsync(filename);
if (!File.Exists(filePath))
return NotFound();
var response = getResponse(filePath);
return ResponseMessage(response);
}
private HttpResponseMessage getResponse(string filePath) {
var response = Request.CreateResponse();
response.Headers.AcceptRanges.Add("bytes");
var streamer = new FileStreamer();
streamer.FileInfo = new FileInfo(filePath);
response.Content = new PushStreamContent(streamer.WriteToStream, GetMimeType(filePath));
RangeHeaderValue rangeHeader = Request.Headers.Range;
if (rangeHeader != null) {
long totalLength = streamer.FileInfo.Length;
var range = rangeHeader.Ranges.First();
streamer.Start = range.From ?? 0;
streamer.End = range.To ?? totalLength - 1;
response.Content.Headers.ContentLength = streamer.End - streamer.Start + 1;
response.Content.Headers.ContentRange = new ContentRangeHeaderValue(streamer.Start, streamer.End,
totalLength);
response.StatusCode = HttpStatusCode.PartialContent;
} else {
response.StatusCode = HttpStatusCode.OK;
}
return response;
}