News for hackers. Stuff that matters.
Re:SecureLogin Authentication Protocol 1.0 by homakov on Sunday June 04, 2017 @11:30AM (#14482027)
It's not common, but the quickest way I could find to reduce # of roundtrip requests. Happy to hear why unacceptable.
Re:SecureLogin Authentication Protocol 1.0 by purvis on Sunday June 04, 2017 @11:49AM (#14482112)
My initial concern was an aggressive server timeout on nginx/haproxy. I think the defaults should be long enough, but it's entirely possible to have something lower than 20 seconds. (and the app developer might not even be aware of this)

I have no reason to think it's unacceptable, was just curious. Interesting project!

Re:SecureLogin Authentication Protocol 1.0 by zwily on Sunday June 04, 2017 @12:58PM (#14482371)
It just means you're tying up a thread (or whole process, if your rails app isn't running with threads) waiting for the response.
Re:SecureLogin Authentication Protocol 1.0 by homakov on Sunday June 04, 2017 @01:05PM (#14482393)
It's not a requirement though: one may ping from the client side with setInterval.