Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
I am doing HTTP wrong
Search
Armin Ronacher
May 13, 2012
Programming
23
5.1k
I am doing HTTP wrong
A fresh look at HTTP for agile languages (more importantly: Python)
Armin Ronacher
May 13, 2012
Tweet
Share
More Decks by Armin Ronacher
See All by Armin Ronacher
The Catch in Rye: Seeding Change and Lessons Learned
mitsuhiko
0
92
Runtime Objects in Rust
mitsuhiko
0
300
Rust at Sentry
mitsuhiko
0
320
Overcoming Variable Payloads to Optimize for Performance
mitsuhiko
0
120
Rust API Design Learnings
mitsuhiko
0
440
The Snowball Effect of Open Source
mitsuhiko
0
300
Mobile Games are Living Organisms, Too
mitsuhiko
0
200
We gave a Mouse an NDK
mitsuhiko
0
730
Debug is the new Release
mitsuhiko
1
560
Other Decks in Programming
See All in Programming
Jakarta EE meets AI
ivargrimstad
0
390
Using Livebook to build and deploy internal tools @ ElixirConf 2024
hugobarauna
0
250
What is Parser
yui_knk
9
4.1k
Evolution of real-time – Irina Nazarova, EuRuKo, 2024
irinanazarova
0
120
rbs-inlineを導入してYARDからRBSに移行する
euglena1215
1
290
『ドメイン駆動設計をはじめよう』中核の業務領域
masuda220
PRO
5
1k
Pythonで改めて考える「クラス(class)」の使いどころ
os1ma
2
560
From Idea to IDE: Developing Plugins for Android Studio
thisaay
1
220
全部見せます! クラシルリワードのSwiftTesting移行プロジェクト
uetyo
0
210
ドメイン駆動設計を実践するために必要なもの
bikisuke
4
330
いつか使える ObjectSpace / Maybe useful ObjectSpace
euglena1215
2
140
Rubyのobject_id
qnighy
6
1.3k
Featured
See All Featured
How to train your dragon (web standard)
notwaldorf
85
5.6k
YesSQL, Process and Tooling at Scale
rocio
167
14k
Mobile First: as difficult as doing things right
swwweet
221
8.8k
GitHub's CSS Performance
jonrohan
1030
450k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
354
29k
Designing Dashboards & Data Visualisations in Web Apps
destraynor
227
52k
Designing on Purpose - Digital PM Summit 2013
jponch
114
6.8k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
41
6.5k
Making the Leap to Tech Lead
cromwellryan
128
8.8k
Thoughts on Productivity
jonyablonski
66
4.2k
Optimizing for Happiness
mojombo
375
69k
Speed Design
sergeychernyshev
22
430
Transcript
I am doing HTTP wrong — a presentation by Armin
Ronacher @mitsuhiko
The Web developer's Evolution
echo
request.send_header(…) request.end_headers() request.write(…)
return Response(…)
Why Stop there?
What do we love about HTTP?
Text Based
REST
Cacheable
Content Negotiation
Well Supported
Works where TCP doesn't
Somewhat Simple
Upgrades to custom protocols
Why does my application look like HTTP?
everybody does it
Natural Conclusion
we can do better!
we're a level too low
Streaming: one piece at the time, constant memory usage, no
seeking.
Buffering: have some data in memory, variable memory usage, seeking.
TYPICAL Request / Response Cycle User Agent Proxy Server Application
Stream “Buffered” Dispatcher View
In Python Terms def application(environ, start_response): # Step 1: acquire
data data = environ['wsgi.input'].read(...) # Step 2: process data response = process_data(data) # Step 3: respond start_response('200 OK', [('Content-Type', 'text/plain')]) return [response]
One Level Up s = socket.accept() f = s.makefile('rb') requestline
= f.readline() headers = [] while 1: headerline = f.readline() if headerline == '\r\n': break headers.append(headerline)
Weird Mixture on the app request.headers <- buffered request.form <-
buffered request.files <- buffered to disk request.body <- streamed
HTTP's Limited signalling Strict Request / Response The only communication
during request from the server to the client is closing the connection once you started accepting the body.
Bailing out early def application(request): # At this point, headers
are parsed, everything else # is not parsed yet. if request.content_length > TWO_MEGABYTES: return error_response() ...
Bailing out a little bit later def application(request): # Read
a little bit of data request.input.read(4096) # You just committed to accepting data, now you have to # read everything or the browser will be very unhappy and # Just time out. No more responding with 413 ...
Rejecting Form fields -> memory File uploads -> disk What's
your limit? 16MB in total? All could go to memory. Reject file sizes individually? Needs overall check as well!
The Consequences How much data do you accept? Limit the
overall request size? Not helpful because all of it could be in-memory
It's not just limiting Consider a layered system How many
of you write code that streams? What happens if you pass streamed data through your layers?
A new approach
Dynamic typing made us lazy
we're trying to solve both use cases in one we're
not supporting either well
How we do it Hide HTTP from the apps HTTP
is an implementation detail
Pseudocode user_pagination = make_pagination_schema(User) @export( specs=[('page', types.Int32()), ('per_page', types.Int32())], returns=user_pagination,
semantics='select', http_path='/users/' ) def list_users(page, per_page): users = User.query.paginate(page, per_page) return users.to_dict()
Types are specific user_type = types.Object([ ('username', types.String(30)), ('email', types.Optional(types.String(250))),
('password_hash', types.String(250)), ('is_active', types.Boolean()), ('registration_date', types.DateTime()) ])
Why? Support for different input/output formats keyless transport support for
non-HTTP no hash collision attacks :-) Predictable memory usage
Comes for free Easier to test Helps documenting the public
APIs Catches common errors early Handle errors without invoking code Predictable dictionary ordering
Strict vs Lenient
Rule of Thumb Be strict in what you send, but
generous in what you receive — variant of Postel's Law
Being Generous In order to be generous you need to
know what to receive. Just accepting any input is a security disaster waiting to happen.
Support unsupported types { "foo": [1, 2, 3], "bar": {"key":
"value"}, "now": "Thu, 10 May 2012 14:16:09 GMT" } foo.0=1& foo.1=2& foo.2=3& bar.key=value& now=Thu%2C%2010%20May%202012%2014:16:09%20GMT
Solves the GET issue GET has no body parameters have
to be URL encoded inconsistency with JSON post requests
Where is the streaming?
There is none
there are always two sides to an API
If the server has streaming endpoints — the client will
have to support them as well
For things that need actual streaming we have separate endpoints.
streaming is different
but we can stream until we need buffering
Discard useless stuff { "foo": [list, of, thousands, of, items,
we don't, need], "an_important_key": "we're actually interested in" }
What if I don't make an API?
modern web apps are APIs
Dumb client? Move the client to the server
Q&A
Oh hai. We're hiring http://fireteam.net/careers