You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find examples for using server-side state in the Haskell ’14 paper and in haste-compiler/examples/chatbox/chatbox.hs, but these rely on liftServerIO, which is not part of the new Haste anymore.
How can server-sider state be implemented with the new remote $ static (import_ f) pattern?
The text was updated successfully, but these errors were encountered:
For 0.6, it's still unclear how this will be implemented, since it will support multiple servers among other things. Currently I'm leaning towards putting this into the same class instance as the routing information, bit this isn't set in stone so suggestions are very welcome.
Haste.App.Simple will probably implement something very similar to liftServerIO for the Server special case, since Simple already provides a Node instance for Server.
In the new Haste.App, server-side state is implemented using the init method of the Node type class, which is executed on node startup. Its return value is used as the environment of the node. Please see the paper for more details.
I find examples for using server-side state in the Haskell ’14 paper and in
haste-compiler/examples/chatbox/chatbox.hs
, but these rely onliftServerIO
, which is not part of the new Haste anymore.How can server-sider state be implemented with the new
remote $ static (import_ f)
pattern?The text was updated successfully, but these errors were encountered: