halo.

_¯_> actually, if using netresendceive in TCP mode, the connection indicator _¯_> should jump to 0 immediately when connection drops. jep. should. if i close pd correctly on the on machine, it closes the port and the connection indicator updates correctly. but if pd crashes, the indicator doesn't update.

i think the netsender would periodically somehow needed to test if the connection is really still alive and try to reconnect periodically if it finds out that the connection was lost. but i can't do that from within a patch. rite?

_¯_> udp shouldnt care at all. mm. but i can't risk a loss of data.

tankes. + joreg.

_¯_> ?

_¯_> Ben Bogart - FMPM/F1999 about Re: [PD] auto connect/disconnect...

_¯_> |Hello Joreg, _¯_> | _¯_> |I've only done one app using netreceive (except the connection was _¯_> |from a tcl script) anyhow I found that when one of the machines crash _¯_> |it takes the port with it, for the machines to reconnect they seem to _¯_> |need another (new) port (or both reboot once one crashes). _¯_> | _¯_> |good luck. _¯_> |Ben _¯_> | _¯_> | _¯_> |On Tue, 2 Apr 2002, Joreg Diessl wrote: _¯_> | _¯_> |> dir list. _¯_> |> _¯_> |> i noticed that the outlet for the connected-status of the _¯_> |> netsend/receive objects is not always correct. when i netsend/receive _¯_> |> between two machines and one of them crashes, the status doesn't _¯_> |> update. _¯_> |> _¯_> |> i'd like two machines to reestablish their tcp-connection _¯_> |> automatically when one of them had to reboot. _¯_> |> _¯_> |> any solutions for that? _¯_> |> joreg. _¯_> |> _¯_> |> _¯_> |> _¯_> | _¯_> | _¯_> | _¯_> |B. Bogart _¯_> |--------- _¯_> |