Hi Matt,

> But in trying to imagine how the auto-save described above would work,
> it seems to me that we are trying to gloss over something in the process
> that has huge significance -- the time it takes to save the data. In
> trying to hide it, we're going to create an app that feels horribly pokey.

I haven't worked with Javascript in years, and I've never done much with
XMLHttpRequest, so I'm probably missing something here.  Can you explain
why the save can't be done asynchronously, with different callbacks
depending on whether the save failed, timed out, or succeeded, while
normal rendering and event handling continues for the user?  That's what
I'd expect to happen here, but again I haven't done much with the
Javascript event loop.

Sincerely,
Jeffrey
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design

Reply via email to