Re: Problem with Connection Manager - isCallInProcess
>Your assessment is spot on, and your proposed fix will remove the
> Hi all,
> status of a connection.
> o.conn is undefined.
> return o.conn.readyState != 4 && o.conn.readyState != 0;
> I believe what is happening is that if the connection is complete,
> the o.conn propery is removed or deleted somehow. "o" still exists,
> but there is no conn property.
> I have a workaround in my local code that checks for o.conn, and if
> it exists, then call isCallInProgress. If not, I assume that the
> connection has completed and continue.
> Hope that makes sense.
error. Thanks for posting this.
This is the proposed revision for the next release.
return o.conn.readyState != 4 && o.conn.readyState != 0;
// The transaction has completed and the object destroyed.