I think I know the answer to this, but I'm going to ask it anyway :-)
There's no way for user code running under bloxtools to store any kind of state or any info at all on the appliance, right? (i.e. outside of the objects that the API provides access to).
Dave
Incorrect. You can store state by just writing to files on the bloxtools server (but beware the security issues if you do this). You can also store state in HTTP cookies if you are developing an HTML interface, and lastly you can always store state in NIOS as extensible attributes on any number of objects.
For example the workflow interface, that was developed before we had scheduled updates, stores the state of all the change in a seperate view(s) that isn't enabled for DNS. (But it gives us database objects where we can store state)
