I tried to clarify some details also for the issue “BOINC Manager interface shouldn’t fully block user interaction when in communicating with client dialog”.
Vitalii Koshura requested to continue the corresponding discussion in the BOINC forum.
Unfortunately, I stumbled on difficulties to reactivate access to my account in this information system.
Thus I hope that chances will become better here to achieve further improvements also for this software.
How do you think about to take another look at the implementation of the function “RPC_CLIENT::get_reply” (according to a test result like the following)?
Markus_Elfring@Sonne:/var/lib/boinc> strace --trace=%network /usr/local/bin/boinccmd --client_version
socket(AF_INET, SOCK_STREAM, IPPROTO_IP) = 3
setsockopt(3, SOL_SOCKET, SO_RCVTIMEO_OLD, "\36\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 16) = 0
connect(3, {sa_family=AF_INET, sin_port=htons(31416), sin_addr=inet_addr("127.0.0.1")}, 16) = 0
sendto(3, "<boinc_gui_rpc_request>\n<auth1/>"..., 59, 0, NULL, 0) = 59
recvfrom(3, 0x7ffda97ba150, 8192, 0, NULL, NULL) = -1 EAGAIN (Die Ressource ist zur Zeit nicht verfügbar)
recv: Resource temporarily unavailable
Authorization failure: -102
+++ exited with 1 +++