Hyperty unable to send HTTP requests across all runtimes

[Endebert]

I would like to ask for a generic solution for hyperties to be able to send http requests.

Currently, there is no set standard for hyperties to do that. For example, the RoomServer hyperty sends HTTP requests using the classes provided by browsers (see here). That means that this hyperty can only run properly in the browser runtime, and would not work in the nodejs runtime.

The RuntimeFactory (e.g. from the browser runtime) provides a generic function for this purpose, so that other parts of the runtime, that have access to this function (like the Runtime Catalogue), can send http requests in a generic matter, unaffacted by which runtime is in use.

However, hyperties lack such access. This might be related to security concerns, however, I request a somewhat similar solution for hyperties.

I would suggest to add another parameter to the hyperty constructor, that is either an object that may hold several runtime specific functions for hyperties, or provide these functions directly as parameters.

@pchainho @sbecot @EwaJan please provide feedback.

Otherwise some hyperties will be limited to the browser runtime, which is not a desired solution, since we would like to have the RoomServer hyperty running in the nodeJS runtime at some point.

[Trikolon]

This issue is still affecting our deployment. No replies since October 2016, please look into it.
So far we were only able to implement this functionality using 'dirty workarounds'. We'd love to see official support for sending http-requests across runtimes.