WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #43316, comment 65


Ignore:
Timestamp:
04/04/2018 09:12:37 AM (4 years ago)
Author:
azaozz
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #43316, comment 65

    initial v1  
    2727> The proposed autosave process I'm talking about here would allow this, but in a very controlled way. Each change would still get a revision, but clients would now have the ability to temporarily persist changes while the user is still working on them.
    2828
    29 So basically you want to move the server auto-saving logic to the client. Not sure this is a good idea. The client can store "persistent backup data" by itself, for example in browser storage. This has nothing to do with server auto-saving. This is now autosaves work at the moment for non-API. There are server autosaves and client (in browser) autosaves.
     29So basically you want to move the server auto-saving logic to the client. Not sure this is a good idea. The client can store "persistent backup data" by itself, for example in browser storage. This has nothing to do with server auto-saving. This is how autosaves work at the moment for non-API. There are server autosaves and client (in browser storage) autosaves.
    3030
    3131Once the client decides to push a server auto-save, the logic for it should be on the server.