This might be a stretch, but it could also be quite cool :)
I would divide dyno start in two: a web proxy that responds to requests
quickly while waiting for the actual service to start. Check out
https://github.com/dblock/heroku-forward - it's an em-proxy that is up
almost immediately and is capable of responding to requests. Right now it
just queues them until the actual web server is started, but it could very
well respond immediately with something like the service is starting. I'd
love a pull request that gives users that option.
On Wed, Dec 26, 2012 at 11:21 AM, Neil Middleton n...@neilmiddleton.comwrote:
Assume that if its taking more than a couple of seconds that this is the
case?
On Wednesday, December 26, 2012, Andrew Lorente wrote:
Hi,
I'm writing a commandline client that consumes a web api that currently
lives in a single web dyno. I'd like the client to be able to tell the user
hey the dyno is starting up; it'll be a second. Short of having the
heroku credentials and asking heroku directly, is there any way to get that
information?
Andrew
--
You received this message because you are subscribed to the Google
Groups Heroku group.
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_US?hl=en
--
You received this message because you are subscribed to the Google
Groups Heroku group.
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_US?hl=en
--
dB. | Moscow - Geneva - Seattle - New York
dblock.org http://www.dblock.org -
@dblockdotorghttp://twitter.com/#!/dblockdotorg
--
You received this message because you are subscribed to the Google
Groups Heroku group.
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_US?hl=en
