Just had a discussion with Tony via ICQ about the cookies and behavior of revert changes. Here is the situation:

1. Open Emplode, open empeg database
2. Power cycle empeg
3. Try to sync, get the expected cookie error
4. Select Revert Changes, emplode gets the empeg database again
5. Try to sync, cookie error occurs again.

Tony is saying this is normal, and emplode needs to be restarted. Now shouldn't revert changes either display a cookie error as well, or better yet, reset the empeg cookie?

Another thought on this as well. It would be nice if emplode could monitor the connection to the empeg, and somehow warn the user that they disconnected with unsaved changes. Then allow a reconnection to the empeg to sync the changes as long as the empeg database didn't change.