[wp-hackers] Autosave

Aaron Brazell aaron at technosailor.com
Mon Jan 2 07:07:41 GMT 2006

> In principle, you could also make use of the memory (e.g. the clipboard).

What on earth are you talking about? The clipboard? As in Windows? What about for non-Windows users?

> Dumping copies to volatile memory wouldn't enable recovery from reboots.
> It
> will, however, compensate for browser crashes, editting 'hiccup' and so
> forth.

What do you think "the clipboard" is?  Maybe you're referring to the pagefile? That's also volatile memory... I'm lost...

> I initially thought about a reserved post slug, which only serves as an
> emergency copy, a last resort. This doesn't have to be anything
> mission-critical. Users would happy enough be restore /any/ bit of lost
> work.

If it has a post slug, or even just an ID which is what unpublished works have, then it has been saved to the database. Or are we referring to the clipboard again?

> I wonder if mouse motion can somehow be detected without JavaScript
> obtrusion.
> It might be useful here.

Only through Flash. Anything you do along these lines needs to incorporate javascript in some way if it is on the client side.

I'm not trying to be hostile and I don't mean to discourage your contributions. 


More information about the wp-hackers mailing list