ftw 0.0.5 → 0.0.6

data/README.md

@@ -61,7 +61,18 @@ I do not plan on exposing any direct means for invoking SPDY.
 
 ## Server API
 
-TBD. Will likely surround 'rack' somehow.
+TBD. Will likely surround 'rack'. Need to find out what servers actually can
+support HTTP Upgrade.
 
 It's possible the 'cramp' gem supports all the server-side features we need
 (except for SPDY, I suppose, which I might be able to contribute upstream)
+
+## Other Projects
+
+Here are some related projects that I have no affiliation with:
+
+* https://github.com/igrigorik/em-websocket - websocket server for eventmachine
+* https://github.com/faye/faye - pubsub for the web (includes a websockets implementation)
+* https://github.com/lifo/cramp - real-time web framework (async, websockets)
+* https://github.com/igrigorik/em-http-request - HTTP client for EventMachine
+* https://github.com/geemus/excon - http client library

data/lib/ftw/version.rb

@@ -1,5 +1,5 @@
 require "ftw/namespace"
 
 module FTW
-  VERSION = "0.0.5"
+  VERSION = "0.0.6"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: ftw
 version: !ruby/object:Gem::Version
-  version: 0.0.5
+  version: 0.0.6
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-02-13 00:00:00.000000000 Z
+date: 2012-02-14 00:00:00.000000000 Z
 dependencies: []
 description: For The Web. Trying to build a solid and sane API for client and server
   web stuff. Client and Server operations for HTTP, WebSockets, SPDY, etc.