Allow Export for HTTP requests to not wait for a response

ID:2029517
 
Feb 3 2016, 12:25 pm
Applies to:
Status: Open
Issue hasn't been assigned a status value.
would it be possible to have an argument that has Export just send the HTTP request and not wait for a response? would be nice for queuing up a webserver to talk back via world.Topic rather than having to wait forever for a response.
Feb 3 2016, 1:00 pm
I'm not sure that makes any difference; the proc is slept when the request gets fired off, and doesn't resume until the request returns or fails. A callback via world.Topic() would actually be the same thing, functionally.
Feb 3 2016, 4:21 pm
sounds like he wants export to return immediately while continuing to execute in the background, so he can write his own callback from the site he export'd to be received as a topic call.
Feb 3 2016, 5:50 pm
spawn(-1) will handle that just fine.
Feb 3 2016, 6:11 pm
that's what I thought as well.
Feb 4 2016, 2:53 am (Edited on Feb 4 2016, 5:00 am)
 
proc/async_export()
  set waitfor = 0
  export(argslist(args))


Use set waitfor = 0 if you don't want the 50,000 to 200,000 cpu cycles spawn overhead to kick in. (spawn overhead is dependant on number of variables in the proc, and the number of items in the sleep/spawn queue, and on rather the proc the spawn is in is an object proc, a global proc, or an overriden built in object/world/client proc) It basically makes the whole proc act like it's encased in a spawn()