2 ms·
It's a little less dangerous when you only need to cooperate with yourself, but yes, it does mean you need to be very careful that you don't have any means for
by Negitivefrags 12y ago
It's a little less dangerous when you only need to cooperate with yourself, but yes, it does mean you need to be very careful that you don't have any means for some requests to take an unexpectedly long amount of time.
In MacOS if you grabbed a window title bar for too long with the mouse then all your sockets would drop. Fun times.
- gioele 12y ago> In MacOS if you grabbed a window title bar for too long with the mouse then all your sockets would drop. Fun times. I wonder if the people developing windowing systems with client side decorations (e.g. Wayland + Qt) thought about this issue. Any information about that?
- mattdw 12y agoAs far as I'm aware there's two approaches (often both used at once) in modern GUI systems that mitigate this. One is an explicit event loop, which can be locked up by user code but not normally by routine events, and the other approach is running the UI on its own thread. (Or, to put it another way, applications should perform any long-running operations not on the UI thread.) The second, particularly, would avoid the dropping-sockets problem, as network and drawing would very likely be on separate threads.
- deleted 12y ago[deleted]