Hello Tooshay,
Welcome to the OptoForums! Your idea of “a table or something” is a good one, since ODL doesn’t do any buffering if the network is down. In particular, you’ll want a PERSISTENT table (the data persists through a power cycle).
You could use a concept similar to what’s in the Message Logging example – which shows how to move messages from the message queue to a persistent table and then set a flag as a trigger for PAC Display (or in this case ODL) to log one sample. If there’s a backlog, it will move one item from the table to a string and then set the flag to trigger that one string to be logged. Then when the notification comes back indicating that one is done, it goes to the next table index for processing, etc.
More examples you might like: FTP/Data Logging Example
http://www.opto22.com/site/downloads/dl_drilldown.aspx?aid=3614
and a few more log-related examples here in the Code Samples and Tips Greatest Hits]:http://forums.opto22.com/t/greatest-hits-and-mini-lessons/443
I hope that helps!
-OptoMary