docs: specify that the RPC endpoint is HTTP/S

[onbjerg]

When foundry-rs/foundry#1003 is merged Forge will support WebSocket and IPC endpoints which should (in theory, at least) significantly speed up forking, since instead of closing and re-opening the RPC at every request, we would keep the connection alive.

As a sidenote, would it make sense to try and compare with a WebSocket endpoint as well? IPC might be a bit too much.

[mds1]

If we just change the below bullet to this, do you think that would be sufficient?

- - "Remote RPC" benchmarks used Alchemy as the RPC provider.
+ - "Remote RPC" benchmarks used Alchemy as the RPC provider, connected over HTTPS.

I am curious to see how performance compares between websockets and HTTPS. I'm not sure offhand if ganache and hardhat support it, but if so maybe we can add a second benchmark comparing those three over websockets?

[onbjerg]

Yeah, that's fine.

And yeah, I agree - if they support it, we should benchmark and compare. Otherwise, it's probably not a fair comparison 😄

[mds1]

Just pushed 2b13971 which updates the docs, created #18 to track websocket benchmarks investigation/support!

[mds1]

Forgot to address IPC: I don't think I've ever come across any real usage/support of IPC either from dev framework or node operators like Infura and Alchemy. (I've also never really looked for it, so I could be wrong). But given that, it doesn't seem worth considering here

[meetmangukiya]

Yeah, I don't think IPC is usable out of local fs. So node operators likely won't have any such support.