[progress Communities] [progress Openedge Abl] Forum Post: Re: Asynchronous Appserver Call...

  • Thread starter Thread starter Laura Stern
  • Start date Start date
Status
Not open for further replies.
L

Laura Stern

Guest
What Johan said is the right idea, but not quite correct. In the event procedure you wouldn't look at ERROR-STATUS:ERROR. You would look at the attributes of the Async request handle associated with the RUN. That is always available as the SELF handle that is set for you by the AVM when in the handler for a PROCEDURE-COMPLETE event. Or you could use hRequestHandle if it is still in scope. Often it isn't, thus the need for SELF. So you would look at SELF:ERROR or SELF:STOP, for example. I also wanted to point out that waiting for the response using PROCESS EVENTS is not very efficient. You can do "WAIT-FOR PROCEDURE-COMPLETE of hRequestHandle" instead. The "Pause n" phrase can be used if you want it to time out. Though normally, you would do this in a GUI app where you are in a WAIT-FOR anyway. Then the normal event processing is going on for the user, but when the AppServer procedure completes, your MyEventProcedure will run.

Continue reading...
 
Status
Not open for further replies.
Back
Top