Re: [liblo] problem sending TCP with lo_send_from()

[Stephen S. <rad...@gm...>]

Sorry, the gmail ctrl-enter "feature" sent my mail without warning
before I was done...

On Mon, Mar 17, 2014 at 5:33 PM, Stephen Sinclair <rad...@gm...> wrote:
> On Mon, Mar 17, 2014 at 3:16 PM, Joseph Malloch
> <jos...@gm...> wrote:
>> Hi all,
>>
>> I've run into a problem: when using TCP, if a previously-unused lo_server is
>> passed to lo_send_from() it can no longer receive at it's declared port. I
>> have attached a simple test program showing this behaviour - tested on OSX
>> 10.9.2
>
> Hi Joe,
>
> I looked at this a bit today but no success yet.  So, just
> acknowledging for now.  FWIW, the output I get with Linux (64-bit) is
> the following:

$ ./test_lo_send_from
created server1: osc.tcp://haptics-PC:13375/
created server2: osc.tcp://haptics-PC:14878/
created address1: osc.tcp://haptics-PC:13375/
created address2: osc.tcp://haptics-PC:14878/
  lo_send_from() server2 -> address1
    server1 received message /ping from osc.tcp://127.0.0.1:50979/
  lo_send_from() server1 -> address2
  lo_send_from() server2 -> address1
    server1 received message /ping from osc.tcp://127.0.0.1:50979/
  lo_send_from() server1 -> address2
  lo_send() -> address1
    server1 received message /ping from osc.tcp://127.0.0.1:50979/
  lo_send() -> address2
  lo_send() -> address1
    server1 received message /ping from osc.tcp://127.0.0.1:50979/
  lo_send() -> address2
server1 url: osc.tcp://haptics-PC:13375/
server2 url: osc.tcp://haptics-PC:14878/


I think in your example you are expecting a "received message" line
after each lo_send_from(), yes?  Definitely a bug.

Steve