S
smat-consulting
Guest
yes, as Thomas is hinting about: storing the request in a table ensures it is not forgotten. What if something happens on the server, and your client is already gone. Nobody will know that the request was either not at all executed, or just partially... I guess, that's why almost every application I know of has some sort of batch-process that's working off a queue or requests. You can mark the request as successful, restart a request if needed, or mark it as failed and - if it was a system failure investigate why it failed; or if it was a business-logic triggered "reject" have the user fix the data-entity and resubmit another request... Asynchronous calls - although appearing elegant, and a handy tool for other situations - are not a good solution for such features...
Continue reading...
Continue reading...