O
OctavioOlguin
Guest
Sorry not to be clear... (english is not my mother lenguaje). What I want to do is to send a signal to the appserver that this computer ir alive (doing somethihing about the app, at laeast). But want that the procedure reporting activity do it's best to inform that, but do it carelessly... if it can't do it, it doesn't care.... as the program would try to infor again in few seconds or minutes... So I imagine this.... Program A is doing something... (that the user commanded) and at finishing it or whatever (to enter another program, or exiting this program, or any other event) it calls keepalive.p, and don't need to wait for it a long time, and don't care if it found the appserver. I just hoped it succeded, and if it didn't, I don't care... This is where I don't want to spend 2 minutes for it to return in case there is no link to appserver. So i call keepalive.p, which collects some info and then in turn it calls putheartbeat.p on appserver and let it run for whatever amount of time it needed so, after calling this putheartbeat.p I immediatelly return, and forget about it is running on appserver... As its sole misión on life of this procedure is to update a record on heartbeat table with the process in turn and the NOW value. Trying to explaing it, I figured aout why it won't worked on testing run.... The keepalive.p procedure is the one doing the connection to appserver and it is the one waiting 2 minutes in case the appserver is out.. So my problem is trying to make a asynchronous call to a local procedure, and forget about it, to keep doing the stuff the user needs... But that is not available, dindn't? I wan to run a local procedure to it's best intent.... and if it won't makes its purpose, don't care, and don't want to wait for it to inform me about it's result.... So my question is about to asynchronously call a local procedure.... I'll change the calling to keepalive.p to asynchronous... Am I in good track? Thanks a lot!!
Continue reading...
Continue reading...