You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some implementations may not be able to publish a Docker container for various reasons, but are able to host a publicly accessible server instance. It would be nice to be able to supply a hostname/port as an alternative.
The text was updated successfully, but these errors were encountered:
That would indeed be nice, but there are a few problems with that:
It only works for servers, not for clients.
We use environment variables to configure endpoint behavior.
For servers, we give them a directory of files to serve before each test case, and after the download we do a byte-by-byte comparison of what the client downloaded.
Performance measurements over the public internet would be hard to compare.
Some implementations may not be able to publish a Docker container for various reasons, but are able to host a publicly accessible server instance. It would be nice to be able to supply a hostname/port as an alternative.
The text was updated successfully, but these errors were encountered: