Discord client being absent/disconnecting is not fatal to the RPC sender, in cases like that we return ErrAgain and in the case of broken pipe (Discord client going away) also reset the Client state so the caller can choose to retry the operation and therefore initiate a new connection attempt.
Signed-off-by: Ophestra Umiker <cat@ophivana.moe>
Since some of the state of the connection is tracked by the Client struct and the Raw method is sufficient for any low-level interaction with the Discord RPC, users of the API should not and does not have any reason to interact with the underlying connection.
Signed-off-by: Ophestra Umiker <cat@ophivana.moe>
Path discovery is ported directly from Discord's C++ example, Windows has a crazy looking socket path that needs special syscall magic to dial, so we'll put that off for the time being.
Signed-off-by: Ophestra Umiker <cat@ophivana.moe>
Ophestra Umiker