On Jan 8, 11:09 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> Just to break up the tension in this thread a little bit, here's my
> idea of what it might look like:
>
> http://sage.math.washington.edu/home/was/tmp/architecture_en.jpg
Factoring Sage into a front end communicating with a Sage kernel is a
very natural idea. Mathematica is divided up this way, and that's
where I've borrowed the names `front end' and `kernel' from. I prefer
`front end' to `notebook server', because the front end could be a
notebook server, or a stand-alone application, or who knows what. And
I prefer `kernel' to `computation engine', because it's shorter. I
presume that Wolfram hasn't trademarked these names, or tried to
patent the idea of dividing a system up into front and rear ends.
So, how hard would it be to make this separation? And (closely
related!) how would you structure communication between the front end
and the kernel?
Cheers,
Peter
--~--~---------~--~----~------------~-------~--~----~
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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
