A
agent_008_nl
Guest
I must confess that I don't know much of pas. If you are right the component specification group could have a look at microservices, if they did not evaluate that architecture already. Thanks beforehand for all those quick replies to the question in my first email then! :-(. Concerning the communication of appserver agent I had a problem in the past (classic appserver), I could not contact idle sessions. This was said to be impossible because of how the agent was built. Exerpts from community.progress.com/.../1674 "a) An AppServer agent is not running the ABL language engine when idle, it is waiting solely on (socket) communications from the AppServer broker b) Running a remote AppServer procedure n-number of times in an attempt to cycle through all the 'idle' agents will almost certainly not produce consistent results" "With regards to 'idle', an AppServer agent works very differently from an ABL client or WebSpeed agent. An AppServer agent is not actively running any ABL procedure when in an idle state; it is actually sitting in an 'C' code idle loop outside of the ABL language interpreter. So no, the agent is not idling in a 'wait-for' where it can be interrupted, timeout, or handle asynchronous [i/o] operations. The agent re-enters the language engine when a client's remote procedure request arrives, exists the language interpreter when the remote procedure has completed, and then waits in its idle loop until the next remote procedure or broker operation is received."
Continue reading...
Continue reading...