Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | vici: Handle closed sockets in the Ruby gem | Evan Broder | 2015-08-24 | 1 | -1/+5 |
| | | | | | | | | | | | | | | | | From recvfrom(2) (which UDPSocket#recv backs into): The return value will be 0 when the peer has performed an orderly shutdown. (i.e. it will return an empty string) Previously in this scenario, Vici::Transport#recv_all would spin forever trying to pull more data off the socket. I'm not entirely clear what happened that caused strongSwan to shutdown the socket, but it probably should not cause vici Ruby apps to spin. Closes strongswan/strongswan#13. | ||||
* | vici: Use default Unix vici socket if none passed to ruby constructor | Martin Willi | 2015-03-18 | 1 | -1/+4 |
| | | | | | While we currently have a static path instead of one generated with Autotools, this at least is congruent to what we have in the Python library. | ||||
* | vici: Make sure to send/recv all requested bytes over socket | Martin Willi | 2014-12-04 | 1 | -3/+22 |
| | | | | | | As the underlying C functions, send/recv on ruby sockets are not guaranteed to send/recv all requested bytes. Use wrapper functions to make sure we get all bytes needed. | ||||
* | vici: Add a ruby gem providing a native vici interface | Martin Willi | 2014-10-10 | 1 | -0/+569 |