- Fri Feb 13, 2015 2:52 pm
#9667
Yep, that's on my todo list. But first, I wanted to implement the espconn_recv_hold and espconn_recv_unhold functions which were added in 0.9.5. I have a draft implementation but I'm not sure it's complete and I don't know how to test that. Any chance you've looked at this?
- Fri Feb 13, 2015 3:45 pm
#9673
I do not use espconn - this is a big mistake, today (SDK 0.9.5) =solid patch, slow speed, allocated big memory, max 4 connections, ...
kadamski wrote:Yep, that's on my todo list. But first, I wanted to implement the espconn_recv_hold and espconn_recv_unhold functions which were added in 0.9.5. I have a draft implementation but I'm not sure it's complete and I don't know how to test that. Any chance you've looked at this?
I do not use espconn - this is a big mistake, today (SDK 0.9.5) =solid patch, slow speed, allocated big memory, max 4 connections, ...
- Fri Feb 13, 2015 3:55 pm
#9674
I agree about espconn not being great but still a lot of examples uses it and I wanted my LwIP version to be a drop-in replacement.
- Fri Feb 13, 2015 4:00 pm
#9676
For what purpose espconn need
Normal programs have not used espconn. This is only for children's studies
Write their own new_espconn version to connect to the LwIP and documentations - is the best option.
kadamski wrote:I agree about espconn not being great but still a lot of examples uses it and I wanted my LwIP version to be a drop-in replacement.
For what purpose espconn need
Normal programs have not used espconn. This is only for children's studies
Write their own new_espconn version to connect to the LwIP and documentations - is the best option.
