On Jul 22, 9:23 pm, William Stein <wst...@gmail.com> wrote: > On Wed, Jul 22, 2009 at 2:19 PM, ghtdak<gl...@tarbox.org> wrote: > > My primary problem is that the Sage subprocess is blocking forever on > > the other side of the pipe when its not computing... Therefore, I > > can't have a Sage sub-process that I'm using in the notebook that is > > also able to communicate with other processes as I can't > > asynchronously receive data (or get timing interrupts). I've gotten > > around this in the past by using threads as it was the only choice I > > had.
Are the following relevant, realistic examples? I wish to... * Start, monitor, stop, and/or steer a long-running computation from a browser. The computation runs in a main loop that periodically checks for incoming messages upon which to act and sends out new messages as necessary. * Share a persistent instance of the Sage kernel among several open worksheets, perhaps with a remote "desktop" capability, to collaborate, teach, troubleshoot, etc. This could be a bit wavy. * Filter data automatically through a sequence of independent worksheet processes. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
