[sr-dev] new dialog module design: tm trigger for dialog management

[Iñaki Baz Castillo]

2010/4/13 Iñaki Baz Castillo <ibc at aliax.net>:
>>> However the solution seems easy:
>>> When a dialog gets confirmed mantain the rest of dialog_out entries
>>> for a while (maybe 3-5 seconds), time enough to ensure that if a new
>>> 200 arrives within an existing early-dialog it will match (an update
>>> properly) such entry in dialog_out. What do you think?

Unfortunatelly I'm trying to figure out this solution and now I don't like it:

- Imagine there are two branches, both with 180.
- Both share the same "dialog_id" field in "dialog_out" table.
- Bob-1 replies 200. The second entry remains 3 seconds before being deleted.
- But before these 3 seconds Bob-2 also replies 200.
- Such 200 would match the second "dialog_out" entry, but then, how to
change its dialog_id field?? In the example it must change from
"1111a" to "1111b".

Any suggestion for it? I leave it as TODO in the wiki for now.

Thanks.


-- 
Iñaki Baz Castillo
<ibc at aliax.net>