I was looking for a better way to do my Network Server commands, so I headed over to the Python IRC channel and asked for some better ways to send text across the network.\u00a0 After some chatting back and forth someone mentioned HTTP and REST, so I started my research.\u00a0 It didn’t take long to find Django (what I used before) and Flask (I saw before, but haven’t used).\u00a0 So I looked around trying to see what the purpose and differences of the 2 are.\u00a0 It was obvious pretty quickly that Flask was the one.\u00a0 My commands and data are pretty basic, so having a micro framework to send and receive made sense.\u00a0 There also seems to be a lot of module attachments to enhance Flask, so future expansion is there.\u00a0\u00a0
<\/p>\n\n\n\n
I have now replaced my basic sockets server with Flask.\u00a0 I have to admit, there’s a lot to like.\u00a0 For one, I can just go to the URL of the sensor in a web browser to view results!\u00a0 Soo very helpful during testing to see if anything looks off.\u00a0 This also opens up possible phone apps that just use a wrapper around a web browser.\u00a0 It would be pretty sweet to use my\u00a0phone to interact with sensors.\u00a0\u00a0<\/p>\n\n\n\n
Definitely a few more possibilities in the near future. I still have to rework some of my unit tests and actually test the program a bit more, since I just overhauled the network service, but so far it’s looking pretty good. <\/p>\n\n\n\n
Lots to do, so back to it I go. <\/p>\n","protected":false},"excerpt":{"rendered":"
I was looking for a better way to do my Network Server commands, so I headed over to the Python IRC channel and asked for some better ways to send text across the network.\u00a0 After some chatting back and forth …<\/p>\n