Attempted fix for https://github.com/hollodotme/fast-cgi-client/issues/18. Implemented option 3 from this comment. This timeout now also applies to the multi requests since the getSocketIdsHavingResponse has been reworked to simply use hasResponse in a loop. This is slower than using stream_select on all resources at the same time, but the only way to accurately determine which sockets have responses.
Tried to figure out a test, but couldn't find way to get a socket/check it's timeout just by having the ID. Should we make a basic getSocketById method publicly available? Or $client->sockets->getById?
Attempted fix for https://github.com/hollodotme/fast-cgi-client/issues/18. Implemented option 3 from this comment. This timeout now also applies to the multi requests since the
getSocketIdsHavingResponsehas been reworked to simply usehasResponsein a loop. This is slower than using stream_select on all resources at the same time, but the only way to accurately determine which sockets have responses.Tried to figure out a test, but couldn't find way to get a socket/check it's timeout just by having the ID. Should we make a basic
getSocketByIdmethod publicly available? Or$client->sockets->getById?