Thursday, August 8, 2019
hmm...
It sounds like you might want to isolate this into a micro-service then. Honestly, and architecturally, it sounds like this process flow might need a redesign, especially as it relies on a resource external to the main application. I am guessing that this is legacy?
Is this application accessed from command line normally?
On Thu, Aug 8, 2019 at 1:09 PM San Ji <sarun101@gmail.com> wrote:
Thank you for the reply, but the client is not a web browser, so no javascript and no polling possible, plus not in our control.--
To be more specific the call to the external service is via a headless browser, not even a direct HTTP call, and you cannot push the data along with the request made by the headless browser.
As I said, there is no obvious way around it business-wise, but it is quite impractical to explain the whole situations, plus some NDA involved.
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/80cfa78d-a199-40a9-8654-0665943b7686%40googlegroups.com.
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAOMcp-BM%3D7KS%2BpTYD4iBkW4tLkqVjRBcO1yZB3X%3DPPwECsqktA%40mail.gmail.com.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment