In the current "bptest" example in the development branch, the storage service is implemented as a separate IPN node number. Where the data interface is assigned node 101 or 102 in the two-hop config, the storage is assigned node 3. This means that the "previous node" block, when sent, will indicate node 3.
In other configurations it is preferable to have the storage service be a sub-service within the data origination interface. For example, this could be service number 1 within the data node 101.
The data model generally supports this configuration, but some changes need to be made in the way queues are forwarded to make it happen
In the current "bptest" example in the development branch, the storage service is implemented as a separate IPN node number. Where the data interface is assigned node 101 or 102 in the two-hop config, the storage is assigned node 3. This means that the "previous node" block, when sent, will indicate node 3.
In other configurations it is preferable to have the storage service be a sub-service within the data origination interface. For example, this could be service number 1 within the data node 101.
The data model generally supports this configuration, but some changes need to be made in the way queues are forwarded to make it happen