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
... huh? What do you envision that looking like, and what would it be used for?
Expression2 eventually got some networking functionality, and it was fairly controversial (security wise) and complicated, but I can't picture much usage of networking outside of having a scripting language, which we're still a fair ways away from.
I could maybe see some limited-purpose networking for specific components, like a Sound Emitter that can play cloud mp3's/youtubes, or a Duplicator pulling from a cloud repo, but I think offering raw GET/POST to users is likely quite far away.
Fair enough, was more thinking about if users wanted to interface with anything outside of s&box which this would make much easier, although I understand the concerns about the security and stuff.
The way I imagined it was having a "Clk" "Address" and then "data" on the POST input and then it would have a string output and maybe a status code output as well that just gets updated when "Clk" is updated.
It seems as though the functionality would be pretty easy to implement using the Http Requests API within s&box.
Im happy to push it down the road for now and focus more on the existing stuff for the time being though.
Adding GET and POST functionality do that data can be gathered from the internet or local network.
The text was updated successfully, but these errors were encountered: