With managed effects, all of the async stuff gets pushed over to the platform.
I suspect that everybody will settle on a reusable `task` type, but each platform can determine its own async scheduling system.
Consider this example:
| "/home" -> q -> res:success <| "<p>howdy " ++ name ++ "</p>"
, name = q |> dict/get "name" |> maybe/default "partner"
| "/contact" -> _ -> res:success "<a href="mailto:hello@example.com">email</a>"
| _ -> _ -> res:notfound "<p>not found</p>"
. res = : success text : notfound text
In this case, the platform creates a simple web server from the following type:
text => query => res
. res = : success text : notfound text
Because scrapscript stays out of the scheduling game, the platform is free to run this code on as many cores and servers as it wants in parallel.
But I 100% agree that community standardization is incredibly important! I just don't have a solution yet :) I will try my best to get everybody to work together though haha
I suspect that everybody will settle on a reusable `task` type, but each platform can determine its own async scheduling system.
Consider this example:
In this case, the platform creates a simple web server from the following type: Because scrapscript stays out of the scheduling game, the platform is free to run this code on as many cores and servers as it wants in parallel.But I 100% agree that community standardization is incredibly important! I just don't have a solution yet :) I will try my best to get everybody to work together though haha