http_relay: 1.0.1-1 in 'melodic/distribution.yaml' [bloom]

[peci1]

Increasing version of package(s) in repository http_relay to 1.0.1-1:

• upstream repository: https://github.com/ctu-vras/http_relay.git
• release repository: https://gitlab.fel.cvut.cz/cras/ros-release/http_relay.git
• distro file: melodic/distribution.yaml
• bloom version: 0.11.2
• previous version for package: null

http_relay

* Noetic compatibility.
* Added sigkill_on_stream_stop so that the relay is only killed if there is a stale request.
* Added sigkill_timeout for automatic restarting of the node even if it hangs on a connection.
* Support NTRIP in Python 3
* Fix Python3 NTRIP relay.
* Initial commit.
* Contributors: Martin Pecka

[clalancette]

This is another name that I think is pretty generic, and I'm actually not sure at all why it needs to be a ROS package. That is, it really just reverse proxies HTTP requests, and the only thing it seems to use ROS for is to get parameters from the global parameter server. It seems to me that this functionality could just be satisfied by pip installing a Python package.

That said, I could be missing something about how it operates, so feel free to correct me.

[peci1]

I agree this functionality isn't directly ROS-related. But it is robot-related. A few times we had devices which could not access outer networks directly.

I searched the whole apt and pip, but i haven't found any simple package for http proxying (except for big beefy frameworks).

And as it wasn't the first time we needed to run a http relay on the robots, I felt this would be a good package candidate.

Our latest use-case is directly embedding the proxy into sensor ROS driver.

I think this package follows the naming REP. The name clearly says what it does. Name collisions don't matter because any other package trying to achieve similar functionality would basically do the same. And org prefix doesn't make sense because there is nothing org-specific there.

[clalancette]

Since Melodic is now EOL, closing this out. I've reproduced the conversation above into #37717.