You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The UDP part can be sequentially used for multiple requests. But the TCP socket is closed upon completion, and hence the second request fails because the socket is closed.
So instead of creating the TCP socket up front (in new, I think it should be created upon actually querying in _tcp_query.
Correct?
The text was updated successfully, but these errors were encountered:
@Tieske I think we can still call tcpsock:new() in resolver.new and just call tcpsock:connect() in _tcp_query. This way we can avoid creating a new TCP cosocket object in every _tcp_query call. What do you think? Patches welcome BTW :)
The UDP part can be sequentially used for multiple requests. But the TCP socket is closed upon completion, and hence the second request fails because the socket is closed.
So instead of creating the TCP socket up front (in
new
, I think it should be created upon actually querying in_tcp_query
.Correct?
The text was updated successfully, but these errors were encountered: