search

sstaub / Ethernet3

Ethernet library for Arduino and Ethernetshield2 / WIZ550io / WIZ850io / USR-ES1 with Wiznet W5500 chip
Other
76 stars 34 forks source link

flush call in parsePacket is slow #16

Closed mtongnz closed 6 years ago

mtongnz commented 6 years ago

Using flush in the parsePacket is a slow way to skip unwanted data. I've modified my fork with code to simply update the pointer on the w5500 so we don't have to transfer it over SPI.

I've only implemented it in the parsePacket function but I think it could work or be better to simply rewrite the flush function with my changes.

I'd like to know if there's a reason for reading rather than skipping unwanted data using flush?

https://github.com/mtongnz/Ethernet3

sstaub commented 6 years ago

Try to rewrite the flush function, test it and make a pull request.

sstaub commented 6 years ago

no answer, so it will closed