converse 1.0.7 → 1.0.8

data/README.md

@@ -18,7 +18,7 @@ that allow the creation of an application-specified API for interacting with pro
 dependency on providers. The application only depends on the API it specifies, i.e. the language it wants to talk.
 
 Brokers become plug-in adapters to providers and can be swapped out at will, provided they can speak the application's
-language as well as the provider's language,. The set of interactions a broker is aware of specifies the API towards
+language as well as the provider's language. The set of interactions a broker is aware of specifies the API towards
 the provider. The application specifies its API through a set of methods that ask brokers to act on its behalf.
 
 Brokers can be chained for multiple translation / technology bridging.
@@ -46,74 +46,74 @@ want to swap the RESTful provider out for a SQL provider, or some other provider
 
 The application specifies the API it wants to talk, and teaches a broker how to discuss transactions:
 
-class ApplicationApi < API
-  def get_transactions(client_id)
-    substance = { 'client_id' => client_id }
-    o = GetTransactions.new(@broker, substance)
-    o.discuss
-  end
-end
+    class ApplicationApi < API
+      def get_transactions(client_id)
+        substance = { 'client_id' => client_id }
+        o = GetTransactions.new(@broker, substance)
+        o.discuss
+      end
+    end
 
 The GetTransactions interaction faces towards the provider, and uses a TransactionTranslator to turn JSON responses
 into a list of transactions that the application understands.
 
-class GetTransactions < ProviderInteraction
-  def initialize(broker, substance)
-    discuss_with_broker_concerning(broker, "transactions")
-    about("<client_id>/transactions.json")
-    detailed_by(substance)
-    by_asking
-  end
+    class GetTransactions < ProviderInteraction
+      def initialize(broker, substance)
+        discuss_with_broker_concerning(broker, "transactions")
+        about("<client_id>/transactions.json")
+        detailed_by(substance)
+        by_asking
+      end
 
-  def interpret_conversation(response)
-    return [] if response.code == '404'
-    TransactionTranslator::build_financial_entries_from(response)
-  end
-end
+      def interpret_conversation(response)
+        return [] if response.code == '404'
+        TransactionTranslator::build_financial_entries_from(response)
+      end
+    end
 
 Generically, the provider interaction knows how to say and ask the provider for information:
 
-class ProviderInteraction  < Interaction
-  def ask
-    @conversation.ask(broker.prepare_content(@concern, @action), broker.generate_parameters(@substance))
-  end
+    class ProviderInteraction  < Interaction
+      def ask
+        @conversation.ask(broker.prepare_content(@concern, @action), broker.generate_parameters(@substance))
+      end
 
-  def say
-    @conversation.say(broker.prepare_content(@concern, @action), broker.generate_parameters(@substance))
-  end
-end
+      def say
+        @conversation.say(broker.prepare_content(@concern, @action), broker.generate_parameters(@substance))
+      end
+    end
 
 The ProviderBroker is taught how to talk the provider's language by using an HTMLConversation:
 
-class ProviderBroker < Broker
-  attr_accessor :host
-  attr_accessor :port
-  attr_accessor :username
-  attr_accessor :password
-
-  def initialize(host, port , username, password)
-    @version = "v1"
-    @host = host
-    @port = port
-    @username = username
-    @password = password
-  end
-
-  def broker_conversation(topic)
-    conversation = HTMLConversation.new(topic)
-    conversation.username = @username
-    conversation.password = @password
-    conversation
-  end
-
-  def open_topic(concern, action)
-    "https://#{@host}:#{@port}/" + concern + "/" + action
-  end
-
-  def prepare_content(concern, action)
-    "/" + concern + "/" + action;
-  end
-end
+    class ProviderBroker < Broker
+      attr_accessor :host
+      attr_accessor :port
+      attr_accessor :username
+      attr_accessor :password
+
+      def initialize(host, port , username, password)
+        @version = "v1"
+        @host = host
+        @port = port
+        @username = username
+        @password = password
+      end
+
+      def broker_conversation(topic)
+        conversation = HTMLConversation.new(topic)
+        conversation.username = @username
+        conversation.password = @password
+        conversation
+      end
+
+      def open_topic(concern, action)
+        "https://#{@host}:#{@port}/" + concern + "/" + action
+      end
+
+      def prepare_content(concern, action)
+        "/" + concern + "/" + action;
+      end
+    end
 
 The application, a dependency injector or a factory at some point decides to use the ProviderBroker to facilitate
 interaction with the provider:

data/lib/converse/version.rb

@@ -1,3 +1,3 @@
 module Converse
-  VERSION = "1.0.7"
+  VERSION = "1.0.8"
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: converse
 version: !ruby/object:Gem::Version 
-  hash: 25
+  hash: 7
   prerelease: 
   segments: 
   - 1
   - 0
-  - 7
-  version: 1.0.7
+  - 8
+  version: 1.0.8
 platform: ruby
 authors: 
 - Ernst van Graan