On 2007-09-28, at 05:55, Kalle Korhonen wrote:
As Trails heavily focuses on domain-driven CRUD applications, it should be a fair assumption that a conversation ends by default once one of C,R or D operation happens. Otherwise, what if each Trails request either opens up or always participates in an existing session? With these, we have an answer to both when the session should be opened and closed, but it would still leave behind lots of open sessions and a bloated use of session if we don't have a strategy to close abandoned conversation
Just my two cents here: Having a view-only page on the objects might help here. A conversation would always start when the users switches from a view page into an edit page and will end when the user presses 'save' or 'ok' and is brought back to a view page.
--
phone +389 -2- 30 64 532 | fax +389 -2- 30 79 495
