Andy Green
Andy Green
> I think in the old version, only the whole message comes, the callback fuction will be called. Well, I think people should be free to think what they like....
No, lws has never done fragment reassembly. In the extreme case it's impossible actually, ws supports fragments each of which can be much larger than any machine's RAM, and you...
> I expected all the message was read at once. It may not all have come at the time we start reading it. It will wake the event loop when...
Turn on the verbose lws logs, it should hopefully give a clue.
This kind of backtrace (it is pointless asking about "a crash" without a backtrace) is caused by leaving a sul scheduled while the object containing it was destroyed. You must...
No any internal use of sul (the old per-wsi timer is done using a sul underneath for a long time) should be handled internally and safe. What is the version...
If you want to use the single per-wsi timer (it seems you are on v4.3) then make sure you have this patch from Jun 5 c6924a57d8523b753d5fd30705ec4a5b08a53f66 it will be there...
It's better to use later stuff generally, v4.4.1 has the patch in.
> I would like to confirm which submitted the modification for this issue? Well... it's good news it is fixed, what's the problem using the later version? v4.3 is deprecated...
No that's not "expected" since a few versions ago (v3.2 IIRC). The event loop will just wait until something to do. If any network events come, it will wake immediately...