Ivan Grokhotkov 7de81270a3 ClientContext: don’t read DataSource in TCP callback ...

Previously, _write_some function would be called each time TCP stack
notifies the application that some data was delivered (via the `sent`
callback). In turn, _write_some would obtain more data to be sent from
the DataSource. In case of a DataSource backed by a Stream, this would
read from a stream. Some libraries (such as SD) may call `yield` and
other blocking operations from Stream read function, which can not be
used in TCP stack callbacks.

This change moves the data sending loop back into the Arduino task, with
a negligible loss of performance. TCP callback now wakes the main task
via `esp_schedule`, which performs stream read and provides more data
to the TCP stack.

Possible future optimization would be to buffer Stream data ahead of
time. That way, buffered data could be sent immediately from the TCP
callback. On the other hand, this optimization would need extra TCP_MSS
of temporary storage, per connection.

Fixes #2399.

2017-05-09 06:17:32 -05:00

..

examples

wifi: add SoftAPModeProbeRequestReceived event handler (#2917)

2017-02-06 13:24:34 +03:00

src

ClientContext: don’t read DataSource in TCP callback

2017-05-09 06:17:32 -05:00

keywords.txt

Update keywords.txt for coloring syntax (#2892)

2017-02-06 13:25:27 +03:00

library.properties

Move esp8266 platform from "arduino" into "esp8266com"

2015-03-27 12:11:55 +03:00