<feed xmlns='http://www.w3.org/2005/Atom'>
<title>suspect-devices/circuitpython/examples/network/http_server_simplistic_commented.py, branch v1.9.2</title>
<subtitle>CircuitPython - a Python implementation for teaching coding with microcontrollers</subtitle>
<id>https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=v1.9.2</id>
<link rel='self' href='https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=v1.9.2'/>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/'/>
<updated>2016-08-05T22:59:51+00:00</updated>
<entry>
<title>examples/network: Split recv- and read-based HTTP servers.</title>
<updated>2016-08-05T22:59:51+00:00</updated>
<author>
<name>Paul Sokolovsky</name>
<email>pfalcon@users.sourceforge.net</email>
</author>
<published>2016-08-05T22:56:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=3d19adf9b323d6b1f907e6825f19b35670bad0d1'/>
<id>urn:sha1:3d19adf9b323d6b1f907e6825f19b35670bad0d1</id>
<content type='text'>
Name recv() based a "simplistic", as it can't work robustly in every
environment. All this is to let people concentreate on proper, read()-
based one (and to turn recv() based into a "negative showcase",
explaining what are the pitfalls of such approach).
</content>
</entry>
</feed>
