On Thu, 2023-12-28 at 13:14 -0800, 'Christian Stewart' via golang-nuts
wrote:
> I agree with what Brian said and would like to suggest the following
> two way RPC library with multiplexing over a single connection of any
> type:
>
> https://github.com/aperturerobotics/starpc
>
There is also
I agree with what Brian said and would like to suggest the following two
way RPC library with multiplexing over a single connection of any type:
https://github.com/aperturerobotics/starpc
On Thu, Dec 28, 2023, 10:06 AM 'Brian Candler' via golang-nuts <
golang-nuts@googlegroups.com> wrote:
>
What do you mean by "Real IP" and in particular how does it differ from the
TCP source address? If the client is behind a NAT, then (a) you won't know
the client's real IP unless they tell it to you (and you trust what they
say), and (b) you won't be able to connect to that address anyway.
If
I have a requirement that requires the rpc server to get the client’s
**real IP** and current connection `net.Conn`.
The reason for needing **real IP** and `net.Conn` is roughly for **two-way
communication**. I hope to be able to send RPC requests to the client of a
specific IP to perform
I was able to make it work
(and no the server is healthy)
I am using legit (https://github.com/icyphox/legit) for my git frontend, it
is like cgit or stagit if you've those before. The default route for repo
page in legit is domain.extension/repository.git, but because running legit
is
