asyncio.start_server example (!)

[cemox]

I am trying to write a simple asyncio.start_server example, but it doesn't function properly.

Code: Select all

import uasyncio as asyncio

async def handle_echo(reader, writer):
    # while (True):
    data = await reader.read(128)
    if (data):
        message = data.decode()
        addr = writer.get_extra_info('peername')
        print("Received %r from %r" % (message, addr))
        print(type(data))

        message = ("HTTP/1.0 200 OK\r\n\r\nHello World \r\n")
        writer.write(message)
        await writer.drain()
    else:
        print("Close the client socket")
        writer.close()
        await writer.wait_closed()

loop = asyncio.get_event_loop()
coro = asyncio.start_server(handle_echo, '0.0.0.0', 80)
server = loop.run_until_complete(coro)

try:
    loop.run_forever()
except KeyboardInterrupt:
    pass

# Close the server
server.close()
loop.run_until_complete(server.wait_closed())
loop.close()

When I connect to my ESP8266 board running the above script from my phone's browser, I see the output in the terminal window (it means connection is ok) like this:

Received 'GET / HTTP/1.1\r\nHost: 192.168.4.1\r\nUpgrade-Insecure-Requests: 1\r\nAccept: text/html,application/xhtml+xml,application/xml;q=0.9,*' from ('192.168.4.2', 50805)
<class 'bytes'>

But, the "Hello World" message does not show up on the browser. But, when I interrupt the script by Ctrl+C and soft reset the ESP8266 board, voila message appears on the browser as expected. What am I missing?

[cemox]

I also noticed that the connections is somehow continues (or suspended), google chrome inspector says

CATION: request is not finished yet

Screenshot from 2020-05-04 19-14-54.png (83.79 KiB) Viewed 9174 times

[pythoncoder]

Alas I don't know the reason. The approach I'd use would be to study working code which uses this approach. I have a copy of Paul Sokolovsky's PicoWeb in this repo. It's an old version but has the (very minor) mods necessary to enable it to work on official firmware. I have tested it on uasyncio V2 and V3. A forum search will turn up other tested web frameworks.

[cemox]

Thank you Peter, I will check PicoWeb. I am glad that I did not ask a stupid question

[cemox]

Things getting more and more interesting. The code blow works, sending http header hundred times, when I change the multiplier to, say, 10, it doesn't work. Do you think it is a bug?

Code: Select all

import uasyncio as asyncio
import utime

async def serve(reader, writer):
    t = utime.ticks_ms()
    resp = b"HTTP/1.0 200 OK\r\n\r\n" + "Ticks = {TICKS}\r\n" *100
    resp = resp.format(TICKS=t) 
    l = yield from reader.read(256)
    print(l)
    writer.write(resp)
    await writer.drain()
    writer.close()
    await writer.wait_closed()

loop = asyncio.get_event_loop()
loop.create_task(asyncio.start_server(serve, "0.0.0.0", 80))
try: 
    loop.run_forever()
except KeyboardInterrupt:
    print("closing")
    loop.close()

[pythoncoder]

I'm no HTML guru but there are some bits of your code I'm not keen on from a uasyncio V3 viewpoint. Here's how I'd write it:

Code: Select all

import uasyncio as asyncio
import utime

async def serve(reader, writer):
    t = utime.ticks_ms()
    resp = b"HTTP/1.0 200 OK\r\n\r\n" + "Ticks = {TICKS}\r\n".format(TICKS=t) 
    l = await reader.read(256)  # yield from may not work
    print(l)
    for _ in range(100):  # More RAM friendly than sending one huge string?
        await writer.awrite(resp)
    await writer.wait_closed()  # The close() call does nothing. This closes the socket.

try: 
    asyncio.run(asyncio.start_server(serve, "0.0.0.0", 80))
except KeyboardInterrupt:
    print("closing")
finally:
    asyncio.new_event_loop()  # Clear uasyncio stored state

The above are just comments on syntax. I'm not clear whether the program logic is correct.

[cemox]

Thank you for your comments Peter. Of course, I did not want to send the same sentence to the client 100 times. I noticed that it woks, if I do that.

In your code, if I change the iteration to 5 for example, it doesn't work either: Browser says: "Safari Cannot Open the Page Because the Network Connection was Lost"

Code: Select all

for _ in range(5): 

This really surprises me.

[cemox]

At last it worked !

Putting a small delay right after

Code: Select all

writer.awrite(resp)

, solved the problem. The whole working code is :

Code: Select all

import uasyncio as asyncio
import utime

async def serve(reader, writer):
    t = utime.ticks_ms()
    resp = b"HTTP/1.0 200 OK\r\n\r\n" + "Ticks = {TICKS}\r\n".format(TICKS=t) 
    l = await reader.read(256)
    print(l)
    await writer.awrite(resp)
    utime.sleep(0.2)
    await writer.wait_closed()

loop = asyncio.get_event_loop()
loop.create_task(asyncio.start_server(serve, "0.0.0.0", 80))
try: 
    loop.run_forever()
except KeyboardInterrupt:
    print("closing")
    loop.close()

[jomas]

At last it worked !

Putting a small delay right after

Code: Select all

writer.awrite(resp)

, solved the problem. The whole working code is :

Code: Select all

import uasyncio as asyncio
import utime

async def serve(reader, writer):
    t = utime.ticks_ms()
    resp = b"HTTP/1.0 200 OK\r\n\r\n" + "Ticks = {TICKS}\r\n".format(TICKS=t) 
    l = await reader.read(256)
    print(l)
    await writer.awrite(resp)
    utime.sleep(0.2)
    await writer.wait_closed()

loop = asyncio.get_event_loop()
loop.create_task(asyncio.start_server(serve, "0.0.0.0", 80))
try: 
    loop.run_forever()
except KeyboardInterrupt:
    print("closing")
    loop.close()

You really should have a look how the http protocol works.
In your code you read 256 bytes. Instead you should read lines until you hit a blank line.
Then you should send your response. But this should better be html code not just text.
After you have send the response you can close the connection

A delay should not be needed if you follow the rules and certainly you should not use 'utime.sleep' because that will block asyncio.
Also better not use 'awrite' because it is legacy code.

[pythoncoder]

@cemox As @jomas says, you should replace utime.sleep with

Code: Select all

await asyncio.sleep(0.2)

The only time you should use utime.sleep in asynchronous code is for extremely short delays which need a precise maximum length. I'm talking milliseconds or below.

@jomas Thanks for the info about HTTP. It's something I should learn.

I hadn't appreciated that awrite is legacy. The twists and turns in asyncio take some keeping up with. I'll update my tutorial and examples in due course.