I'm in the process of separating some behavior out into a separate service (separate heroku app), but in the meantime the service resides within the same heroku app as the action which needs to call the service. (Think myservice.com making a call to api.myservice.com which are both served from the same heroku app).
Therefore if the action makes a call over http to the service, and it happens to get routed to the same dyno which is handling the initial request, the dyno will block until timeout. If it gets routed to a free dyno, then everything is fine because the free dyno returns a response to the blocking dyno, which then finishes the request and unblocks. Is there any way to guarantee that the service call won't be routed to the same dyno? If there is a free dyno, will it always receive the request over a blocking dyno? Thanks, Doug -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
