-
Notifications
You must be signed in to change notification settings - Fork 87
Refactor the Wiki for a post-#121 incarnation of Server
with multiple protocols.
#126
Comments
Refactor Reel::Server, refactor/retrofit/abandon SocketMixin, depending on #126 immediately hereafter.
HTTPS also needs more information about recently added options refactored in #124 |
Did rapid-fire Wiki updates. Yardocs seem to be dynamically generated. @tarcieri are you cool with me drafting and posting FAQ and Mailing List content here? |
Sure |
@tarcieri I just put the FAQ text directly in since you can change it directly as you see fit. I think the FAQ text can probably be posted to the mailing list. I kept it brief, simply, and calm rather than causing fear and trepidation about it. |
@tarcieri you should probably post to the mailing list so people actually read it sooner than later. I figure the FAQ text is enough, after your edits if you have any, then that can be checked off and this can be closed... and then we're all done, allowing #123, #124, and #125 to gracefully come in, when ready. |
For now, at least the Wiki is correct. |
Catch up... to celluloid#126
Posted to the mailing list: https://groups.google.com/d/msg/celluloid-ruby/uKKuZbRNwR4/jsPFY13eghEJ |
Right now in the Wiki, before #121, all previous implementations of Reel were done directly through
Reel::Server
which was implied to be HTTP but now must explicitly beServer::HTTP
. This will break every use ofReel
in the wild, asReel
transforms into being multiprotocol by design.Now we have
Server::HTTP
,Server::SSL
, and as of #123 there isServer::UNIX
... a natural fourth protocol ought to be a directly usable implementation of the a la carte websocket handler, as aServer::WebSocket
option I believe, but that is a separate issue. That could alternatively beServer::SSL::WebSocket
andServer::HTTP::WebSocket
, so discussion is needed on how to package that. Again, separate issue.The Wiki needs to be refactored to reflect the state of
Reel::Server
, and backward-facing documentation ought to be written to address the change toReel::HTTP
until the previous way is out of memory andServer::HTTP
is widely known in the existing coders depending onReel
.Reel::Server
change to support many protocols, and how to add more protocols ( linking to a separate page, proposed: Howto Add Protocols toReel::Server
)The text was updated successfully, but these errors were encountered: