Tuesday, November 9, 2010
testub es website update
I spent tonight optimising my code for efficiency and to avoid potential catastrophic crashes.
While I don't anticipate getting DDOSed in the few hours that I will have the site running in connection with the tube filler, I wanted the experience to be as fair as possible to all involved.
I have implemented a method of checking the user's ip, and assigning that ip to each request that they make to have a tube dripped. When their request exceeds 5 they get a message saying so, and that they should wait an hour before they can have another go.
The flood limit I chose (5) is pretty low however because of the limited size of the tubes I don't want one person to be able to completely fill any one tube straight away without giving anyone else a go. I think this will piss people off, but I'm just trying to be fair.
I also have put in the ability to insert an array of IP addresses to be excepted from the rule; I have added my home IP address to this list and will be adding the uni IP address too, so that the different people using my site don't get locked out.
I have also implemented a limit on how many triggers a single tube can take; I will calibrate this value to equal the number of drips it takes to nearly overfill the tube.
When any one tube has been overfilled it is highlighted in red, and is no longer clickable. I only implemented the block out client side, so if someone really wants to overflow a tube they could curl the script at the server, but they will only get 5 goes until the server blocks their ip.
The current implementation isn't optimum, but it is fairly quick. (execution time is ~ 1/1000 sec.
It turns out my exhibition space now includes a TV, so I was going to just have the website live on the tv, with the comments and graph auto-updating, but after testing today it turned out the TV res is shit, so I have had to write a new section of the site so I can have just the graph and comment sections taking up the whole screen (I optimised it for the full screen mode in Chrome)
Comments
Add a comment
If entered, the twitter username field is used to subscribe to replies to your comment. When someone replies, a tweet will be posted to @yourusername.
All comments are moderated before being posted, so be nice.
All fields are optional, your twitter username will not be public if you choose to put it in
Tags
- 50mm
- COD
- Finn
- HDR
- Liam
- MIDI
- OP-1
- OP1
- addon
- albert park
- alpine
- anonymous
- aperture
- application
- arduino
- arduino_grapher
- audio trigger
- avatar
- backpack
- beach
- blackwork
- blog
- break
- c++
- capacitor
- cats
- cnc
- code
- concert
- crossing
- deeplinking
- diy
- electronic
- electronics
- exhibition
- experimental
- fabrication
- finn
- fire
- flash
- fp
- from scratch
- glass
- high speed photography
- high speed sync
- hotlinking
- icanhazcheezburger
- installation
- interface
- isaachenry.com
- javascript
- jquery
- juggle
- juggling
- lens
- lightpainting
- lol
- long exposure
- lowepro
- ludwig
- me
- microcontroller
- midi
- night
- ofxOP1
- one
- openframeworks
- pcb
- photography
- photography trip
- photoshoot
- php
- portrait
- post
- processing
- project365
- public
- reblogging
- redirection
- reset
- rss
- sand
- sensors
- sequencer
- sky
- sleeve
- smash
- soldering
- splash
- tattoo
- telephoto
- test
- testub es
- testubes
- testubes website jquery php
- three
- timelapse
- tongariro
- tornado
- two
- typewriter
- waterspout
- website
- website ajax
- wifi
- wind
- work

