-
Leigh B Stoller authored
1. web_tasks: This table is to track background processes that we start either from the web interface or from the protogeni XMLRPC interface. The goal is to not have a bunch of task specific stuff in tables, but a more general way to start a process tied to an object (say, like taking an image) and record state of the process in the descriptor (say, the image size as it grows). A client can poll for info about the process; the server just looks for the task descriptor associated with the object and returns the (currently) adhoc data in JSON format to the client. Work in progress, still determining if this general approach is worth it. 2. web_sessions: Playing with real PHP sessions, using the DB to store the session data (instead of the default, which is data files in /var/run). No idea how I am going to use this one, just want to play with sessions.
b0c5f6e9