Possible concurrency issue - events not being executed sequentially. about fsock

[danbogos]

hey @csiwek

Good to hear from you (in one way happy you have issues ;) ).

Will make the possibility to have it synchronous there and close this issue when done.

DanB

[csiwek]

thanks Dan,
I'm looking forward for your patch...
I was just wondering if you have experienced similar issue...?

[danbogos]

@csiwek, yes it did happened to us as well (eg: HANGUP before CHANNEL_CREATE) but we did not bother blocking there since I am not 100% FS sends them in order (although there are chances it does).

DanB

[danbogos]

hi @csiwek

Looking at the issues, I see this one still being opened. Did u work-around it? As said I cannot testify that FS sends events in order.

DanB

[csiwek]

Hi @danbogos

For now, we have ended up by not executing the handlerFunc as a new goroutine (which I mentioned in the first post) and doing it when necessary inside those functions . This definitely fixes issues we were having so I guess FS is trying to keep events in the right order. I understand you probably will never experience this issue because the way you are using FS. Our application behaviour highly relies on the actual call state

[danbogos]

Thanks for the update. Please reopen if you think changes are needed.

Have a good one and see you most probably at ClueCon!

DanB