protocol-rack 0.18.0 → 0.19.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4fed6d6b2ffc0dc007d343e8f9414af4c61cd7c321cb289b6d218290977feb7f
-  data.tar.gz: d02dd7e216b58d3bbe94e5e99b4c71d689ad8de5cb7451a67a81bcd0ade5a55a
+  metadata.gz: 5864594e5fdeb7192006dc95ccc3d448a0c9b953e331f2df4a9bacad898309d5
+  data.tar.gz: 056de84f70c904d064de318a532ea46ae1568e6882568a7c965f767696d984d9
 SHA512:
-  metadata.gz: df29bd96d8542e75e146d0eec4d7813f7e037fdd84e68bd08ac1f6a4cfca66b3ec176dd3167e31eedb3ae849b44059c23b0fe57a4aea8b4a2c3f55c90755b36f
-  data.tar.gz: 6969ef3c4a7fb95083dd57697c5bcf0aee57ec1f9eee6f0b4233af56e4845513c21480cee2abc14daf320d5cf7c5c739b50448bc3d3c6023432292a6544d8876
+  metadata.gz: 5567e929cdedd1a8bdc9595d1b25c36b918bda3fe107c8e36af47af5a9fa95f8aaa311de7454df88c3dfecc437dd45c55b3763465314225ffa1902958d03423c
+  data.tar.gz: c34f91c5a27fdccf962fe1738b6aeb23022c83e4923c7190ecede735d78cf3bb6dd5a9a6757148ee5b17e1e5750f9e2751dc90905efb42255e88ed916966016c

data/context/getting-started.md

@@ -53,3 +53,25 @@ end
 ```
 
 The adapter automatically detects your Rack version (v2, v3, or v3.1+) and uses the appropriate implementation, ensuring compatibility without any configuration.
+
+### Server Adapter
+
+Any Rack compatible server can host `Protocol::HTTP` compatible middlewares.
+
+``` ruby
+require "protocol/http/middleware"
+require "protocol/rack"
+
+# Your native application:
+middleware = Protocol::HTTP::Middleware::HelloWorld
+
+run do |env|
+	# Convert the rack request to a compatible rich request object:
+	request = Protocol::Rack::Request[env]
+	
+	# Call your application
+	response = middleware.call(request)
+	
+	Protocol::Rack::Adapter.make_response(env, response)
+end
+```

data/lib/protocol/rack/adapter/rack2.rb

@@ -131,10 +131,10 @@ module Protocol
 							meta[key] = value
 						elsif value.is_a?(String)
 							value.split("\n").each do |value|
-								headers[key] = value
+								headers.add(key, value)
 							end
 						else
-							headers[key] = value
+							headers.add(key, value)
 						end
 					end
 					

data/lib/protocol/rack/adapter/rack3.rb

@@ -103,10 +103,10 @@ module Protocol
 							meta[key] = value
 						elsif value.is_a?(Array)
 							value.each do |value|
-								headers[key] = value
+								headers.add(key, value)
 							end
 						else
-							headers[key] = value
+							headers.add(key, value)
 						end
 					end
 					

data/lib/protocol/rack/version.rb

@@ -5,6 +5,6 @@
 
 module Protocol
 	module Rack
-		VERSION = "0.18.0"
+		VERSION = "0.19.0"
 	end
 end

data/readme.md

@@ -17,60 +17,14 @@ Please see the [project documentation](https://socketry.github.io/protocol-rack/
 
   - [Request and Response Handling](https://socketry.github.io/protocol-rack/guides/request-response/index) - This guide explains how to work with requests and responses when bridging between Rack and `Protocol::HTTP`, covering advanced use cases and edge cases.
 
-### Application Adapter
-
-Given a rack application, you can adapt it for use on `async-http`:
-
-``` ruby
-require "async"
-require "async/http/server"
-require "async/http/client"
-require "async/http/endpoint"
-require "protocol/rack/adapter"
-
-app = proc{|env| [200, {}, ["Hello World"]]}
-middleware = Protocol::Rack::Adapter.new(app)
-
-Async do
-	endpoint = Async::HTTP::Endpoint.parse("http://localhost:9292")
-	
-	server_task = Async(transient: true) do
-		server = Async::HTTP::Server.new(middleware, endpoint)
-		server.run
-	end
-	
-	client = Async::HTTP::Client.new(endpoint)
-	puts client.get("/").read
-		# "Hello World"
-end
-```
-
-### Server Adapter
-
-While not tested, in theory any Rack compatible server can host `Protocol::HTTP` compatible middlewares.
-
-``` ruby
-require "protocol/http/middleware"
-require "protocol/rack"
-
-# Your native application:
-middleware = Protocol::HTTP::Middleware::HelloWorld
-
-run do |env|
-	# Convert the rack request to a compatible rich request object:
-	request = Protocol::Rack::Request[env]
-	
-	# Call your application
-	response = middleware.call(request)
-	
-	Protocol::Rack::Adapter.make_response(env, response)
-end
-```
-
 ## Releases
 
 Please see the [project releases](https://socketry.github.io/protocol-rack/releases/index) for all releases.
 
+### v0.19.0
+
+  - Use `Headers#add` instead of `Headers#[]=` in Rack3 and Rack31 adapters, which is the correct interface for appending headers.
+
 ### v0.18.0
 
   - Correctly invoke `rack.response_finished` in reverse order.

data/releases.md

@@ -1,5 +1,9 @@
 # Releases
 
+## v0.19.0
+
+  - Use `Headers#add` instead of `Headers#[]=` in Rack3 and Rack31 adapters, which is the correct interface for appending headers.
+
 ## v0.18.0
 
   - Correctly invoke `rack.response_finished` in reverse order.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: protocol-rack
 version: !ruby/object:Gem::Version
-  version: 0.18.0
+  version: 0.19.0
 platform: ruby
 authors:
 - Samuel Williams