Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me.
cwilt Senior Member Joined: 20/03/2012 Location: United StatesPosts: 147
Posted: 06:19am 20 Jul 2013
Copy link to clipboard
Print this post
TZA, this discussion has been very good. I have been trying to figure out where I would use tasks instead of events and interrupts. For me, using tasks on a micro controller project is new.
Currently the wifly holds an IO high as long as a client is connected. IO going high triggers interrupt routine. Inside that routine I cancel the rising edge interrupt and wait for html request. The request is responded to and a falling edge interrupt is enabled. The falling interrupt is triggered when the client disconnects and does the final clean up and turns the rising edge interrupt back on. The slowest part of the web server is finding the html file, opening, reading and printing to the wifly serial port.
I hope this discussion continues.
cwilt Senior Member Joined: 20/03/2012 Location: United StatesPosts: 147
Posted: 06:21am 20 Jul 2013
Copy link to clipboard
Print this post
I turn video off whenever speed and memory is required.