Now that we send a single big message, the receipt of the ack is now tied to the runtime cost of eval.
That is, long evaluations will fail. We should reorganize the code a bit for Android such that the ack can be read immediately w/o re-introducing out of order message arrival
One simple way maybe to schedule the result write via a setTimeout?
Now that we send a single big message, the receipt of the ack is now tied to the runtime cost of eval.
That is, long evaluations will fail. We should reorganize the code a bit for Android such that the ack can be read immediately w/o re-introducing out of order message arrival
One simple way maybe to schedule the result write via a
setTimeout
?