I started writing software in 1984. Over the years I worked with many languages, technologies, and tools. I have been in leadership positions since the early 2000s, and in executive roles since 2014.
I am not sure if this what you are looking for, but a local (to the conference) Proxy server is how this kind of thing is usually done.
It functions as a cache. If your requests are mostly GETs with no parameters, they are served from the local cache. The user is completely unaware of the caching. You can also make the caching more aggressive and cache some GETs with parameters (for example, search results).
Usually, the biggest problem is the WiFi connection. I have never seen that kind of thing work flawlessly in large conferences such as Re:Invent. There are always some issues.
A peer-to-peer solution would probably create even more problems due to the increased WiFi traffic.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I am not sure if this what you are looking for, but a local (to the conference) Proxy server is how this kind of thing is usually done.
It functions as a cache. If your requests are mostly GETs with no parameters, they are served from the local cache. The user is completely unaware of the caching. You can also make the caching more aggressive and cache some GETs with parameters (for example, search results).
Usually, the biggest problem is the WiFi connection. I have never seen that kind of thing work flawlessly in large conferences such as Re:Invent. There are always some issues.
A peer-to-peer solution would probably create even more problems due to the increased WiFi traffic.