Skip to content
This repository was archived by the owner on Dec 18, 2018. It is now read-only.

Use pre-encoded headers if possible#491

Closed
JunTaoLuo wants to merge 1 commit intodevfrom
johluo/preencoded-headers
Closed

Use pre-encoded headers if possible#491
JunTaoLuo wants to merge 1 commit intodevfrom
johluo/preencoded-headers

Conversation

@JunTaoLuo
Copy link
Contributor

Kestrel update after pre-encoded bytes are added to StringValues in dotnet/extensions#68

@benaadams
Copy link
Contributor

May need to delete some lines in the generated ClearFast methods to get the full benefit of this change: #493

@benaadams
Copy link
Contributor

Added PR for that issue "Faster Headers.ClearFast" #497

@halter73
Copy link
Member

Would there be a perf hit to use pre-encoded StringValues instead of using the special-cased FrameResponseHeaders.SetRaw(Connection|Date|TransferEncoding|ContentLength|Server) methods like we do today?

@JunTaoLuo
Copy link
Contributor Author

Revisiting this right now. Instead of rebasing on top of a month of work, I'll open a new PR.

@JunTaoLuo JunTaoLuo closed this Jan 16, 2016
@JunTaoLuo JunTaoLuo deleted the johluo/preencoded-headers branch January 22, 2016 19:35
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.

4 participants