On Tue, Oct 14, 2008 at 8:26 PM, Jason Grout <[EMAIL PROTECTED]> wrote: > >> >> Actually, the concept Timothy is talking about is true. The framework >> for running notebook processes in Knoboo is very different from what >> Sage does to serve notebooks. Indeed, the machine running actual >> notebook processes (or engine processes as we call them) is considered >> history in this situation, however, access to the notebook data would be >> absolutely un-affected -- an important point -- because users *can* >> still view/download their notebook data as it is maintained by an >> entirely separate system running on a physically separated machine. Not >> to be nit-picky, but this is very attractive from a user perspective; >> it's not as catastrophic as the entire service disappearing (like what's >> happening now). > > > > If I understand things correctly, the biggest obstacle to Sage doing > this currently is that the client processes expect to be able to read > and write the notebook files (the files associated with the cells in the > notebook) and the server expects the output to automatically appear in > the correct cell directory. Is that correct?
Yes. In fact, as long as you have a shared filesystem for both machines, you can *already* run the worker processes on a different real or virtual machine. -- William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
