Hello Sir, Can you please explain the third point. Here you have mentioned that earlier in lwc and aura, request to server were boxed and all requests within the box shared the same governer limits. How continuation pattern was earlier useful in this limitation?
Knowing Salesforce, They would not deprecate to support backward compatibility. @future is still available even though Queueable is available, there are many more examples
@@ajai.a2374 I needed Continuation when I had to chain multiple async requests to fetch response in chunks. Response was too big to be sent in one call.
thanks for the detailed explanation. The only video I could find in youtube about this.
Hey man, Thanks for the information, really helpful I really appreciate it !
Hello Sir, Can you please explain the third point. Here you have mentioned that earlier in lwc and aura, request to server were boxed and all requests within the box shared the same governer limits. How continuation pattern was earlier useful in this limitation?
Very informative
It helps to achieve a request-reply pattern for integrations with high latency... kindly suggest how can we achieve it without continuation
Continuation still has same limitations that of normal HttpRequest.
If it is not usable any more then ideally it should have been deprecated
Knowing Salesforce, They would not deprecate to support backward compatibility. @future is still available even though Queueable is available, there are many more examples
It's still useful for callouts to external services.
Can you share a scenario where this will be useful?
@@ajai.a2374 I needed Continuation when I had to chain multiple async requests to fetch response in chunks. Response was too big to be sent in one call.