On Tue, 2020-03-31 at 13:19 +0200, IOhannes m zmölnig wrote:
> On 3/31/20 12:40 PM, Christof Ressi wrote:
> > Now you can send messages between the two sockets. See attached
> > patch.
>
> incidentally (well not so much i guess), this topic has also been
> covered by a few other threads on this
> On 31 Mar 2020, at 21:22, Fred Jan Kraan wrote:
>
> Hi All,
>
> I would be happy to add abstractions based on maintained objects from other
> libraries to the maxlib library (where I caused all this trouble by removing
> the instable tcp-objects).
>
> Greetings,
>
> Fred Jan
Nobody
Hi All,
I would be happy to add abstractions based on maintained objects from
other libraries to the maxlib library (where I caused all this trouble
by removing the instable tcp-objects).
Greetings,
Fred Jan
On 31/03/2020 21.03, Edwin van der Heide wrote:
On 31 Mar 2020, at 09:21,
On 3/31/20 9:01 PM, Edwin van der Heide wrote:
> I was assuming that a (TCP) socket would be a requirement to be able to send
> data up and down without port forwarding on both sides but I guess I’m wrong
> here.
this (that you cannot do bi-directional communication with a
connectionless
> On 31 Mar 2020, at 09:21, IOhannes m zmölnig wrote:
>
> On 3/30/20 11:03 PM, Edwin van der Heide wrote:
>>
>
>>> in any case, you need to solve the problem of interleaved messages from
>>> multiple clients.
>>
>> Yes you are right about iemnet/tcpclient vs mrpeach/tcpclient. And yes, I
>>
Hi Roman,
> On 30 Mar 2020, at 23:40, Roman Haefeli wrote:
>
> Hey
>
> On Mon, 2020-03-30 at 20:16 +0200, Edwin van der Heide wrote:
>
>> Here is more context:
>> - What I’m interested in is to create a small and 'super simple'
>> internet ensemble in which multiple participants are playing
On 3/31/20 12:40 PM, Christof Ressi wrote:
> Now you can send messages between the two sockets. See attached patch.
incidentally (well not so much i guess), this topic has also been
covered by a few other threads on this mailinglist and on pd-dev and on
github:
Hm. I see bidirectional connections with [netsend]/[netreceive] working
only for TCP. Also, the help-file says 'send' for [netreceive] works
only for TCP.
Yes, but the problem is only about [netreceive -u]: it doesn't store a
list of clients, so [send( can't work.
Actually, the implementation
On Tue, 2020-03-31 at 09:16 +0200, IOhannes m zmölnig wrote:
> right.
> with recent Pd's you can implement the [udpsndrcv] abstraction using
> [netsend -u -b].
Hm. I see bidirectional connections with [netsend]/[netreceive] working
only for TCP. Also, the help-file says 'send' for [netreceive]
On 3/30/20 11:03 PM, Edwin van der Heide wrote:
>
>> in any case, you need to solve the problem of interleaved messages from
>> multiple clients.
>
> Yes you are right about iemnet/tcpclient vs mrpeach/tcpclient. And yes, I
> understand that solving the interleaved messages is important but
On 3/31/20 12:06 AM, Christof Ressi wrote:
>
> On 30.03.2020 23:31, Peter Venus wrote:
>>
>> a good starting point to solve this is in using [udpsndrcv] from
>> iemnet.
>
actually [udpsndrcv] is just an abstraction around [udpclient] to
implement the object of the same name from mrpeach.
>
>
>
11 matches
Mail list logo
