• consequat (unregistered)

    Could be something to do with preventing double-clicking on the button which could cause multiple accounts being created because the back-end processes couldn't get certain redundancy prevention data in place quickly enough.

  • Flannel (unregistered)

    Each time management complained it was too slow or they needed to look good they'd decrease the delay by a bit.

    Alternatively someone with no idea of race conditions and how to fix them.

  • Sean (unregistered)

    Having a huge delay on login for FAILURE is common to stop spambots. Doing it on every single login is definitely a WTF -- it won't hurt the spam bots but it'll definitely hurt real users.

    Doing it on signup would in theory slow down a spam bot from creating a ton of requests, but given that most of them probably make multiple simultaneous requests (probably from multiple machines) and given that there are far more effective anti-bot measures for signup forms, I'd consider it a minor WTF to delay on these.

  • sota (unregistered) in reply to diaphanein
    diaphanein:
    Code Dependent:
    public void lay() { try { Bed.sleep(getGirlfriend()); } catch (InterruptedException ignored) {} }
    Fails to link: unresolved symbol "getGirlfriend"

    private HotelRoomAdultMovie getGirlfriend() { return(_movie); }

    public void lay() { try { Bed.sleep(getGirlfriend()); } catch (InterruptedException ignored) {} }

    Captcha: acsi - drunk character table

  • Alan8 (unregistered)

    First!!

    (I have a slow connection...)

  • ElClowno (unregistered)

    Maybe it's something about the application does. I remember a driver for a scanner that had a delay between scanning 2 pages, too. The reason was a law in place at this time that limited the maximum number of scans per minute due to copyright reasons. With a driver in another language it worked pretty well.

Leave a comment on “Delaying the Evitable”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article