RESTful Rational Arduino
After spending some time with a few arduinos and a stack of weird shields it dawned on me that writing application specific code to flash to the arduino every time I come up with an idea was stupid.
I spent some time pondering the best way to abstract this, by ponder I mean drink beers, chase girls, and not think about it. Then it dawned on me that addressing this in a RESTful way could keep me from having to flash my arduino ever really. At least in prototyping.
Pyaler has some really awesome applications that I am fairly uninterested in. The most obvious being home automation. I live in a subletted condo and can flip a light switch by myself usually. I’m fairly certain some sort of awesome use will pop into my head here in the next week or so though. I don’t have a flock of arduinos to manage, but it’s nice to know I could if I did.
RESTduino is similar on a smaller scale and has less dependancies. Currently I’ve been using a Processing sketch to handle OSC (Open Sound Control) signals and hand them over to the arduino outputs. I like this because I can use TouchOSC on my iphone for fast testing/troubleshooting. I’m really hoping to adopt this process to simplify.
I’ll be tearing both of these apart this weekend and really figuring out my stack. Wish me luck.
-
partiessexgroupsex liked this
-
youngadultsbrutalbukkake liked this
-
readymaid liked this
-
millerhooks posted this
