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
Currently, the simple_message receive calls will block forever until the requested message data is received or the connection is dropped/reset. For some applications, it may be helpful for the user to be able to specify a timeout on the socket-read.
The recent fix to Issue #25 helps provide some of the low-level socket structure needed for this enhancement. But, this enhancement will require additional changes to the higher-level messaging layers to pass the timeout error status up to user-level code.
The text was updated successfully, but these errors were encountered:
See also ros-industrial#34. Existing receive functions are unaffected, and behave
exactly as before. The only big difference is that all classes
inheriting from `SmplMsgConnection`, i.e., `SimpleSocket` must now
override a `receiveBytes` member function with a timeout
parameter. (So if any other classes inherit from `SmplMsgConnection`,
they will need to be updated.)
Currently, the simple_message receive calls will block forever until the requested message data is received or the connection is dropped/reset. For some applications, it may be helpful for the user to be able to specify a timeout on the socket-read.
The recent fix to Issue #25 helps provide some of the low-level socket structure needed for this enhancement. But, this enhancement will require additional changes to the higher-level messaging layers to pass the timeout error status up to user-level code.
The text was updated successfully, but these errors were encountered: