No, post-handling is the right one, not post-processing ...

[hub.git] / application / hub / main / handler / message-types / class_BaseMessageHandler.php

diff --git a/application/hub/main/handler/message-types/class_BaseMessageHandler.php b/application/hub/main/handler/message-types/class_BaseMessageHandler.php
index d04acc1f7dba70751cc835dccdffe90aca6d9415..2eff41a6b96311eb0e903f5bb8a27cb0dcdca385 100644 (file)
--- a/application/hub/main/handler/message-types/class_BaseMessageHandler.php
+++ b/application/hub/main/handler/message-types/class_BaseMessageHandler.php
@@ -71,6 +71,24 @@ abstract class BaseMessageHandler extends BaseDataHandler {
                // Let the DHT facade do the work
                $this->getDhtInstance()->registerNodeByMessageData($messageData, $this);
        }
+
+       /**
+        * Posty-handles data array of the message
+        *
+        * @param       $messageData            An array with message data to handle
+        * @param       $packageInstance        An instance of a Receivable class
+        * @return      void
+        */
+       public function postHandleMessageData (array $messageData, Receivable $packageInstance) {
+               // Get current entry from stack
+               $messageData = $packageInstance->getStackInstance()->getNamed(NetworkPackage::STACKER_NAME_PROCESSED_MESSAGE);
+
+               /*
+                * Feed hash to miner by handling over the whole array as also the
+                * sender and tags are needed.
+                */
+               $packageInstance->feedHashToMiner($messageData);
+       }
 }
 
 // [EOF]