Http Client Functions (fetch)

[raphael-goetz]

Add the Http Client (& websocket) as well as fetch functionallity

[nicosammito]

@raphael-goetz Could you give some more details on how you are planning to implement all these functionalities on the runtime?

[raphael-goetz]

We did discuss to take the JavaScript fetch function as a reference for this.
You would just give in a HTTP_REQUEST and would get a HTTP_RESPONSE back. As for the implementation: ist just a http client.

In theory there's also no problem on the runtime doing streaming via web socket but this feature also could be an action.

[nicosammito]

Okay I would implement a fetch function. For ws how did you plan that on the runtime?

Because in theory you are opening a connection to a specific endpoint and receive message. So it would mean that we have a function definition that would take in a HTTP Request and 2 consumers, one for streamed messages and one for failure / disconnect.

But how would you implement the sending of messages?

@raphael-goetz

[nicosammito]

@raphael-goetz any info?

[raphael-goetz]

We need to make sure that inside of a stream calling s respond would not stop the flow from executing.

I would make a new respond like function that would not end the flow but continues executing but sending the current result to the adapter.

[nicosammito]

We need to make sure that inside of a stream calling s respond would not stop the flow from executing.

I would make a new respond like function that would not end the flow but continues executing but sending the current result to the adapter.

But this doesn't answer my question. I understand how we receive messages, but how to you send messages? Because this would be a separate function and how does it now the connection to use?

[raphael-goetz]

Let's just talk about in the evening.