There are a number of tickets like #12232 (maybe six or seven) related to the simple server API. This thread is to discuss the status of this. Here are a few possible opinions.
1) This API hasn't worked for a long time well, and doesn't work at all with the current notebook. So these tickets are unlikely to ever be worked on in their current state and should be closed. 2) We are removing these files from Sage, but not sagenb, in #11409, so we should close them as irrelevant. 3) Same but we should not close them since we like to keep track of upstream project's progress. 4) We should keep them, no question. Apparently the Sage cell isn't quite the same thing, as it isn't (currently) a persistent thing. I have no idea whether cloud.sagemath has anything to say about this. Thanks for any responses; if this is truly dead, it would be useful to close these, but if it's still not in that bad of shape, it would be nice to keep them open and then open a metaticket for re-establishing the simple server API. - kcrisman Keshav has an interesting comment related to this: wrt sage tickets vs sagenb tickets, I feel like sagenb might be reabsorbed into sage at some point. People split it off as a separate project so they could rapidly redo it in Flask, but development has really trailed off since that big push in 2011, and Sage is switching to git anyway so sagenb doesn't need to be a separate project to take advantage of DVCS nimbleness. Plus now there's cloud.sagemath.org and the ipython notebook so in the future sagenb might be fighting a war on two fronts (as a multi- user UI and a single-user UI respectively) to stay relevant as a project. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
