#7254: [with patch; needs review] sagenb notebook: automatic worksheet 
refreshing
and synchronization
---------------------------+------------------------------------------------
   Reporter:  was          |       Owner:  boothby     
       Type:  enhancement  |      Status:  needs_review
   Priority:  major        |   Milestone:  sage-4.2    
  Component:  notebook     |    Keywords:              
Work_issues:               |      Author:              
   Reviewer:               |      Merged:              
---------------------------+------------------------------------------------

Comment(by schilly):

 Replying to [comment:5 was]:
 > Good question.  I think what will happen is that if you do something,
 say insert a cell, evaluate a cell, change a cell, and that entire
 transaction gets dropped, then a refresh will end up being forced.  You
 will (1) loose that change, and (2) see that it didn't take.  This is
 probably much better than thinking that you made that change but actually
 not making it.

 Well, that could also happen, probably. What I was thinking about is a
 flaky connection (or one, where a roundtrip takes longer than 2 secs).
 Then, the async request is still open, but already some others waiting to
 get dispatched. The number of requests is limited (FF 6, IE 8 in dial up
 mode only 2, older browsers also only 2) and therefore all the new
 requests timeout eventhough the network might be ok. What i propose is a
 boolean request_state_flag that is set to true when the request is made
 and set to false, when the async callback 'refresh_cell_list_callback' is
 in success or in timeout/fail. Then, the request should only be made if
 the flag is false and it never happens that many simultaneous requests jam
 the network.

 I just don't know all the details and what's already done by the async
 requests, so that's just a very rough description what i'm thinking about.

 Reverting valid new content to an older version just because of bad timing
 with the server might be another issue. Updates from the client to the
 server must have higher priority.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7254#comment:6>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to