Websocket blocks

[Joel Bodenmann 4]

We're going to add websocket blocks in the next few days. Those blocks will allow your processes to talk to other systems via websockets. This will also allow you to build a web UI using regular HTML & JS technologies to send & receive data to & from your processes during execution. This will allow to easily create dashboards based on web technologies without the need for any web server.

 

Right now there are three blocks panned:

  - Connection

• Input: IP address
• Input: Port
• Output: Connection (can be connected to the blocks below)

  - Receive

• Input: Connection (from the 'Connection'  block).
• Output: Payload (most likely a single string value)

  - Send

• Input: Connection (from the 'Connection'  block).
• Input: Payload (most likely a single string value)

 

Any thoughts on this?

[printmaster 0]

Would this websocket block also allow us to access data from Web-API's? 

[Joel Bodenmann 4]

Those blocks would allow to communicate with any system that implements the websockets protocol. Any "Web-API" that implements the websockets protocol would therefore be "accessible" using these blocks.

 

However, these blocks would not allow to communicate to REST APIs (which is what the kids these days tend to refer to as "Web-API"). We will provide separate blocks for those cases soon.