Closed albertolluch closed 6 years ago
This is not a bug.
This is how TCP protocol works: only a single application can be bound to a port. The UDP protocol does not have this issue for example.
By default, both the client and server will try to bind to port 31415 as specified by the pSpace specification.
This can be circumvented in two ways by:
NewRemoteSpace
will use instead of localhost
.I see the problem. Let's discuss this when you start implementing repositories and gates.
Commands like
s.Get(&x)
on a remote spaces
seem to incorrectly block even if there are matching tuples ins
.Minimal example:
Server source:
Client source: