Skip to content
This repository has been archived by the owner on Nov 20, 2018. It is now read-only.

Change SendFileAsync to use a fallback implementation instead of throwing #497

Closed
wants to merge 4 commits into from

Conversation

davidfowl
Copy link
Member

…wing

- If the user wants to use the SendFile API directly then they can access the feature
explicitly.

#496
}
if (!File.Exists(fileName))
{
throw new FileNotFoundException(string.Empty, fileName);
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not just put fileName instead instead of string.Empty?

- Removed SupportsSendFile
- Don't check for existence, let FileStream throw
- Updated Doc comments
- Pass the buffer into StreamCopyOperation
- Using a real using instead of try finally.
@davidfowl davidfowl closed this Dec 3, 2015
@davidfowl davidfowl deleted the davidfowl/fallback-sendfile branch December 3, 2015 08:01
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants