Hi - I'm evaluating Heroku for a web service that will be hit hard by a ton of iPhone users.
As I understand it, each "dyno" handles one connection at a time. So, N dynos means N connections at a time. This rules out doing any form of keep-alive on read and chunked transfer on write since these would tie up a dyno for just one client connection. Is this understanding correct? I'm expecting multiple service calls in bursts (say 3 requests in a keep alive) and a single interested party would love to see the results of those requests (chunked transfer, long polling). I suppose if I cannot use keep alive or chunked transfer effectively then I'll have to revert to multiple service calls instead of keep alive and polling instead of chunked transfer or long polling. Thoughts? Please let me know if I'm missing something. Thanks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
