From a67e03d3d4050a1365d20d50e6e6e02845314deb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebastian=20Buczyn=CC=81ski?= Date: Fri, 20 Dec 2024 18:47:33 +0100 Subject: [PATCH] Review of chapter 22 --- chapter_22_fixtures_and_wait_decorator.asciidoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/chapter_22_fixtures_and_wait_decorator.asciidoc b/chapter_22_fixtures_and_wait_decorator.asciidoc index 188dc65c..59dafdec 100644 --- a/chapter_22_fixtures_and_wait_decorator.asciidoc +++ b/chapter_22_fixtures_and_wait_decorator.asciidoc @@ -104,6 +104,7 @@ _Being an attempt to explain sessions, cookies, and authentication in Django._ ((("authentication", "cookies and"))) Because HTTP is stateless, +// SEBASTIAN: I remember me, being a junior always puzzled when reading HTTP is stateless. Perhaps an explanation in plain english (periphrasis) would do a better job. It's a second sentence in part that tries to explain something tricky. servers need a way of recognising different clients with _every single request_. IP addresses can be shared, so the usual solution is to give each client a unique session ID, @@ -495,6 +496,8 @@ One of the fun things this can be used for is to make a decorator that changes the arguments of a function. But we won't get into that now. The main thing is that our decorator now works! +// SEBASTIAN: that's actually an awful idea, making it harder to leverage type hints. I wouldn't be giving people such ideas :D + [subs="specialcharacters,macros"] ----