Haste.HPlay.WebSockets

Hplayground WebSockets have de-inversion of control. it uses wsAsk for syncronous request-responses.

wsAsk can also handle asynchronous traffic too since it catches every received message, not only the next message

For an example, see http://tryplayg.herokuapp.com/try/hplay-sockets.hs/edit

Documentation

wsOpen :: URL -> Widget SockId

open the socket and continue the flow when it is opened.

wsAsk :: (JSType a, JSType b) => SockId -> a -> Widget b

syncronous request-responses. wsAsk can also handle asynchronous traffic too since it catches every received message, not only the next message and executes the rest of the computation as is usual in a active widget

wsClose :: SockId -> Widget ()