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

Performance penalty on huge response objects #1

Open
burakdede opened this issue Apr 16, 2014 · 0 comments
Open

Performance penalty on huge response objects #1

burakdede opened this issue Apr 16, 2014 · 0 comments
Assignees

Comments

@burakdede
Copy link
Owner

There can be performance penalty on huge response objects by directly reading them into memory so it would be nice to have response stream. User can call direct type-safe content string or call content stream and handle response by himself.

@burakdede burakdede self-assigned this Apr 16, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant