News for hackers. Stuff that matters.

A comment on Why JWTs Suck as Session Tokens (2017). Parent comment

Re:Why JWTs Suck as Session Tokens (2017) by cwyers on Thursday August 30, 2018 @11:50AM (#17877670)
> It's 2018 and you're complaining about a few MB of bandwidth

Ah, yes, 2018, the Year Where Everything On The Internet Is Connected To A Cable.

[ Parent | on HN ]
Re:Why JWTs Suck as Session Tokens (2017) by lostcolony on Thursday August 30, 2018 @12:20PM (#17877930)
It's 298 bytes per page request given the example he gives (your token can be smaller or larger depending on the data in it).

It's 24 MB of bandwidth to the -server-. Your server -better- be behind a decent broadband connection, or what are you even doing?

1/3rd a kilobyte per page request to the -client-. 1/3rd a kb is a blink of an eye even on modern dialup.

[ Parent | on HN ]
Re:Why JWTs Suck as Session Tokens (2017) by neop1x on Monday September 03, 2018 @08:27PM (#17905738)
Why do you think it has to go skyrocket forever?! I am already really disgusted by how big applications are nowadays, how bloated, slow, memory-hungry and inefficient they are. Every saved MB counts.
[ Parent | on HN ]
Re:Why JWTs Suck as Session Tokens (2017) by pythonaut_16 on Thursday August 30, 2018 @12:28PM (#17878009)
In this case the article is talking about 24 MB of additional bandwidth used by the server to serve 100k pageviews using JWTS
[ Parent | on HN ]