Improve Support of Thin and Swiftiply
Reported by Matt Todd | February 6th, 2008 @ 10:31 PM | in Release 0.5.0
With both Thin and Swiftiply providing excellent performance and balancing/clustering, as well as handling numerous tasks such as PID files and logs already, it almost seems redundant that Halcyon handles these things as well.
This needs to be addressed. (Another ticket will be put in to suggest moving some of the server functionality out of Server::Base and into Server and appropriate handlers/adapters.
But for Thin and Swiftiply, these servers should be the primary concern and support goal for Halcyon (as of now).
Ebb might also be interesting.
Comments and changes to this ticket
-
Matt Todd February 7th, 2008 @ 01:50 AM
- Milestone changed from “Release 0.4.0” to “Release 0.5.0”
- State changed from “new” to “open”
Belongs with 0.5.0 Milestone.
-
Matt Todd February 9th, 2008 @ 09:59 PM
Big news, Thin now has Swiftiply client support baked right in... awesome. Perhaps we should just tailor Halcyon to sit right on top of Thin...
But do we really want to limit ourselves in such a way? (Even though it's not really a limitation right now, the future may provide an even better option.)
I think we should focus on integrating with Thin, but provide a slender layer through the Handlers module for Thin, Mongrel, etc. This provides flexibility in the future, for folks to use Mongrel when they choose not to have Thin, and Thin normally.
-
Matt Todd February 26th, 2008 @ 01:49 AM
- State changed from “open” to “resolved”
Will be addressed as part of #13 with the move to being completely dependent on Rack (and Thin).
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.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Matt Todd