G
Garry Hall
Guest
If I understand this correctly, there are a couple of things you seem to want: threads (to do the connection/communication with the appserver asynchronously while still processing business logic) and unreliable communication to the appserver. The AVM does not provide threading. You cannot make an asynchronous call to a local procedure. Asynchronous appserver calls require a connection to the appserver, the connection itself cannot be handled asynchronously. If you expect your appserver to be periodically unavailable, then this possibly won't work for you. This sound like you want to send UDP messages rather than TCP messages: connectionless and unreliable. You might want to consider alternatives. OE doesn't provide UDP, so you could wrap your own with DLL calls or .NET. You'd have to handle the server side too, probably not as an appserver, but a batch client. You also want to receive a response on the client in case the message was received, in which case you'd have to periodically check for a response (and make sure you do this in the client AVM's main thread). Another alternative might be to address the appserver's unavailability, so you don't have to deal with it. This would guarantee that every async request would get a response, which contradicts one of your stated goals, although that goal was to deal with the appserver's unavailability. I don't really understand how "killing a persistent procedure" comes into this, so I might be missing something critical.
Continue reading...
Continue reading...