session-initiate and session-accept are sent before setLocalDescription succeeds

[fippo]

While sending the offer/answer before setting the localdescription likely decreases call setup time, it is potentially unsafe since setLocalDescription might fail.

Causes jitsi/jitsi-meet#31 currently.
Getting the local ssrcs from the created answer instead of the localdescription might be a better solution to this problem.

[paradisaeidae]

Roll #35 into this.

[paradisaeidae]

Does anyone have a strategy for handling this?
I see it when connection negotiation latency exists.
MarkT

[fippo]

The time difference between doing this before or in setLocalDescription is ~25ms so that should not be noticable.

[paradisaeidae]

I do not have rigorous testing regime in place atm.
Though the recent build has passed this error and continued to connect.
I can say that Chrome (browser) cheats to get it's apparent speed.
It loads javascript files 'in background'.
They are not actually rendered into usable code even though 'loaded'.
So far I've had to use setTimeout to circumvent this being an issue.

A.T.Best!
MarkT