#66 ✓invalid

Could "address" be a host instead of an IP?

Reported by Carl | April 20th, 2008 @ 11:24 PM | in 0.8.2

Instead of specifying an IP as "address", i'd like to be able to specify a host name.

This doesn't make sense when Thin runs as a regular server, but makes a lot of sense when it runs as a Swiftiply client.

On dynamic addressing environments such as EC2, it's much more convenient to use host names instead of IPs, as the latter change all the time.

I guess this is something pretty easy to implement. If the input is not an IP, you can assume it's a host and resolve to IP, and just use that IP from then on as you'd normally do.

Does it make sense?

Comments and changes to this ticket

  • Carl

    Carl April 20th, 2008 @ 11:52 PM

    Actually, now that I think about it, it's probably not a good idea to discard the host name once it's been resolved.

    Ideally, you'd resolve it everytime Thin tries to connect to Swiftiply. I believe Thin will try to reconnect to Swiftiply if the connection breaks, is that correct?

    If you keep the host name around, it's useful because the IP to which the host name resolves can and will likely change.

  • macournoyer

    macournoyer April 21st, 2008 @ 10:06 AM

    • Milestone set to 0.8.2

    Works for me:

    I mapped dev.com to localhost in /etc/hosts file then

    thin start -a dev.com

    Then I can access from http://dev.com:3000

    Is that what you mean?

  • macournoyer

    macournoyer May 15th, 2008 @ 10:36 PM

    • State changed from “new” to “invalid”

    works for me, reopen if you got more info

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

People watching this ticket