RE: shutting down VXI

["Walker, William J (William)" <wjw@avaya.com>]

Title: RE: shutting down VXI

I recalled that VXI itself does not start a separate thread,
(my platform creates the thread for the VXI to execute in, for
each new call)... so my question is then how to cause VxiApiRun
to break out of it's VXI::document_loop().   I assume the only
way is to return an error code from one of the callback methods
that I implemented (e.g. VXIPromptQueue).

-----Original Message-----
From: Jean-Michel Reghem [mailto:jeanmichel.reghem@advalvas.be]
Sent: Thursday, April 19, 2001 10:20 AM
To: vxi-discuss@metronomicon.com
Subject: Re: shutting down VXI

Walker, William J (William) écrivait ( Thursday 4/19/01 09:30 AM ) dans le
message ci-dessous:
---

>Once a platform has started a executing a session via VXIapiRun(url),
>what is the proper way to cleanly stop the session if the platform
>detects that the remote end disconnects?  Will calling VXIapiDestroy()
>from the platform's thread cleanly stop the script and shut down the
>VXI thread?

Yes...for me, it's the only solution... in the reference doc, it's writed:
"This call (VXIapiDestroy) is the reciprocical of VXIapiCreate and should
be called when a given VXI object is no longer needed. Typically this
called at the end of each call."

But I answer by another questions:
*When we do that, what's the VXIResult of VXIapiRun ???

   VXIresultSUCCESS   VXIresultERROR   VXIresultNOTENOUGHMEMORY
VXIresultNO_INTERFACE    VXIresultUNEXPECTED
   VXIresultFAIL     VXIresultPOINTER   VXIresultHANDLE
VXIresultACCESSDENIED   VXIresultBAD_INLINE_SYNTAX
   VXIresultINVALIDPARAM   VXIresultIOERROR   VXIresultTIMEOUT
VXIresultFATALERROR   VXIresultJSERROR
   VXIresultJSEXCEPTION    VXIresultHUNGUP   VXIresultNOTSUPPORTED  ??????

And what about VXIapiGetResult(vxi,&val) in this case?

>Thanks,
>BW
>
>Bill Walker
>Avaya Inc.
>wjw@avaya.com
>1-732-817-4609
---