Topic: Widget Cycling, CPU and memory management? (for Production Model)
I noticed from another post that the production model will be opening a new thread per Flash play instance. Does that also mean the each thread has isolated memory management? In addition, if threads are stored in the background is the processor utilization limited? Feel free to point me to the wiki if I over looked some documentation.
I gather that the Chumby is pretty open ended right now. Any documentation on the widget cycles and threads would be wonderful (for the production model). If we are not killing the various widgets threads in the background can a widget demand focus? For instance, is a widget that checking for e-mail limited by it's cycling time? Or can it be checking for e-mail even if it's not being displayed. I assume that Control Panel will have to demand focus in some form.
In addition, other then using a USB hard drive is any local storage available, possible in the form of a Swap. Is there any way that multiple Widgets can communicated with each other locally or do we need to conduct all widget communication via the web? From what I read it looks like there is absolutely no local data what so ever (excluding the USB HD option). I was hoping that something like the Flash ExternalInterface existed but... alas it's not part of Flash Lite2, however, read/write access would be required. Is it possible to do any kind of temp file saving using a Unix swap folder so that widgets could talk to each other locally?
Thanks again for the help.