Hi! You've got there a few good points! I was hoping that playback could be based on requests only. More I think of it, it would need to save responses, too.
To answer your questions: 1. Errors perhaps need not to be saved. Although, when everything is saved it may lead to a huge amount of space, such a log would be finite, 1 year backwards or so. 2. The playback system would fake the original request. Session variables can be tricky, though, but what is needed is recreating the pages and forms user has submitted or viewed. Not to execute them again! So session variables may not be that necessary. 3. Actually, playback could be in theory be run without a database at all. The aim is to find an exact point when some specific change in the database has occurred and who did it, and to document it. I know, this looks like a Big Brother, but in medical applications it may be required by law, in my country at least. Regards, Zdravko -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/ad6d67ff016733f16e048fa63032c79e%40ruby-forum.com. For more options, visit https://groups.google.com/d/optout.
