-
1. Re: Conversation Timeout and time of conversation destructio
gavin.king Dec 17, 2006 6:30 PM (in response to ccurban)This is the correct behavior.
-
2. Re: Conversation Timeout and time of conversation destructio
ccurban Dec 17, 2006 6:39 PM (in response to ccurban)What exactly is the correct behaviour?
What I am heading at:
Is the conversation destroyed after a timeout, when the user the conversation belongs to does something again?
Or is the conversation destroyed after a timeout, when any user does something? -
3. Re: Conversation Timeout and time of conversation destructio
gavin.king Dec 17, 2006 6:58 PM (in response to ccurban)The first one.
-
4. Re: Conversation Timeout and time of conversation destructio
ccurban Dec 17, 2006 7:16 PM (in response to ccurban)Thanks Gavin.
I need to "unbound" some entity from the current user (i.e. change a status in the database), if his conversation times out, to be able to distribute that entity to another user again.
Is there any actual "SEAM-way" to be notified when the conversation really times out, or am I looking in the complete wrong direction to solve that problem?
And with time out I mean the conversation-timeout setting. -
5. Re: Conversation Timeout and time of conversation destructio
gavin.king Dec 17, 2006 7:22 PM (in response to ccurban)I really, really don't think its a good idea to try and update the db from *any* kind of timeout.
Remember, the server can always crash.
Are you trying to implement some kind of offline pessimistic lock? -
6. Re: Conversation Timeout and time of conversation destructio
ccurban Dec 17, 2006 7:40 PM (in response to ccurban)You're right (thanks for reminding me of that)
I really, really don't think its a good idea to try and update the db from *any* kind of timeout.
and you're rightAre you trying to implement some kind of offline pessimistic lock?