@Kevin: A revision is always stored in the DB (in the node_revisions table IIRC) and hence it *is* saved. So it would simply show up in the list of revisions, meaning that if the user can access the revisions, he can access the preview revision as well.
But I'm sure David is talking about some UI enhancement that would allow the user that would ask the user if he'd like to edit his last unpublished revision (i.e. a preview) when the user edits a node.

@David: IMO the interim preview revisions should be deleted.
And the ability to go back to your last unpublished revision (last preview) should also take a special case into account: what if /another user/ has updated the node after your last unpublished revision? The user should be warned in this case, or he might unknowingly erase new content by that other user.

Wim

On Jun 7, 2007, at 21:29 , Kevin Reynen wrote:


And how would the average user find a previewed but not saved revision? 

Is that something only users in a role with access revisions could recover?

- Kevin Reynen

On 6/7/07, David Strauss <david@fourkitchens.com> wrote:
With clever use of revisions, we could eliminate the preview system
entirely from the codebase.

Here's how it would work. If a user clicks Preview, it creates a new
revision but does not mark it as the current revision. The preview seen
is the new revision rendered. If a user clicks Save, it creates a new
revision *and* marks it as the live one. Optionally, we could then
delete the interim preview revisions.

Another advantage to this is that a user can work on a node, preview it,
and have their work saved. If a user comes back and edits the node with
unsaved previews, they can choose to work from the latest preview or the
latest public revision.

I know Drupal 6 goes a long way to fixing previews, but this would
eliminate all inconsistency.