Tommy Rampal Posted July 28, 2011 Share Posted July 28, 2011 Hey again all,So pretty much my GUI actively does HTTP requests and waits for the body upon a user interacting with it. That's fine, until I noticed something..For testing purposes, I just hammered through my own built menus/interfaces to get to what I wanted to test to (I've made my own 'panel' system that checks for server variable changes when a panel is changed), I noticed that I managed to crash my script my clicking too fast: "Too many HTTP requests too fast. (Set HTTP_VERBOSE_THROTTLE, FALSE in the parameters to hide these messages.)"Luckily I have implemented a time-out on my scripts for when a user abandons the GUI without finishing appropiately, or a HTTP failure (e.g. my web server is down). But for users who know where they want to be with the GUI, or those in a rush, this can be quite an inconvenience.Has anyone else worked with this problem and/or does anyone have any advice for a practical work around? Sorry if this is an easy fix, I'm just about to head to bed and thought it'd be quicker if I wake up to a solution tomorrow ;) Link to comment Share on other sites More sharing options...
Please take a moment to consider if this thread is worth bumping.
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now