This functionality is essential for me, so opening a new issue. It has overlap with: #8
I want to make a application that has full server functionality, but can send message from the same socket/address. Looking at the server and client module of gosc, in the server there is a shutdown function, it probably handles non-blocking better (?), it can specify it's own udp address/port. Assuming that the server module is optimal for server functionality, why would I use the client module for it?
See for a example the lo_send_from() function in liblo:
http://liblo.sourceforge.net/docs/group__liblo.html#gaa4a314562b09e2fd00749a5d0b4d0955
I think this is perfectly in line with 'OSC best practices' as quoted in the other issue.
edit: scgolang/osc uses a more fundamental type UDPConn (an OSC connection over UDP, client or server), which you can send from:
https://pkg.go.dev/github.com/scgolang/osc#UDPConn
https://github.com/scgolang/osc/blob/v0.11.1/udp.go#L99 (Send, SendTo)
This functionality is essential for me, so opening a new issue. It has overlap with: #8
I want to make a application that has full server functionality, but can send message from the same socket/address. Looking at the server and client module of gosc, in the server there is a shutdown function, it probably handles non-blocking better (?), it can specify it's own udp address/port. Assuming that the server module is optimal for server functionality, why would I use the client module for it?
See for a example the lo_send_from() function in liblo:
http://liblo.sourceforge.net/docs/group__liblo.html#gaa4a314562b09e2fd00749a5d0b4d0955
I think this is perfectly in line with 'OSC best practices' as quoted in the other issue.
edit: scgolang/osc uses a more fundamental type UDPConn (an OSC connection over UDP, client or server), which you can send from:
https://pkg.go.dev/github.com/scgolang/osc#UDPConn
https://github.com/scgolang/osc/blob/v0.11.1/udp.go#L99 (Send, SendTo)