More socket stuff. Your input is needed.
Posted: Fri Mar 20, 2015 10:35 am
Previously, all socket data was held in an alternate thread and only exposed to the Lua side through MicroMacro's event system. After rewriting a good portion of the code, this is no longer the case. Any data that a socket receives can be requested at any time in your scripts without causing any blocks, like so:
The data will still also be available via the "socketreceived" event. As of right now, even if you use socket:recv() to grab and pop a message off its input queue, that same message will also be passed to macro.event() later as a socketreceived event, and vice-versa; the two do not modify each other. This also means that any data not popped off the queue will still remain in it until popped off, and not be automatically flushed each logic frame. This is where your input comes in.
Should already-read messages (popped off the queue from socket:recv()) still be passed as an event?
Should the socket:recv() queue be flushed every logic cycle? (Note: any unhandled messages would be flushed *after* the events)
Is there any other functionality needed?
Code: Select all
-- This will display all information held in the socket's receive queue before moving forward
local data = socket:recv();
while( data ) do
print("More data:", data);
data = socket:recv();
end
Should already-read messages (popped off the queue from socket:recv()) still be passed as an event?
Should the socket:recv() queue be flushed every logic cycle? (Note: any unhandled messages would be flushed *after* the events)
Is there any other functionality needed?