search

reTHINK-project / specs

You'll find here the full detailed specification of reTHINK Framework
Apache License 2.0
3 stars 3 forks source link

Runtime Core and MN: single Address Allocation functionality #18

Open pchainho opened 7 years ago

pchainho commented 7 years ago

Currently, we have runtime address allocation functionalities duplicated into Runtime Registry and the Sync Manager. The proposal is to have a new generic Address Allocation runtime component that is in charge of any kind of address allocation including Hyperty Addresses and Data Object allocations. The runtime address of the new component would use the suffix \address-allocation

In the same way the MN currently has two address alocation functionalities and the proposal is to have just one using also the suffix. \address-allocation

You can find the spec for the new proposal at:

sdruesedow commented 7 years ago

Will the "scheme" field be mandatory then? Or shall the "hyperty" scheme be the default, if no scheme is given?

pchainho commented 7 years ago

yes, "scheme" is mandatory for this message

sdruesedow commented 7 years ago

OK, from MN's point of view I see no problems with that proposal.

sdruesedow commented 7 years ago

Please verify the implementation of the address-allocation for hyperties in the runtime and the Vertx MN! As agreed above and defined in the message specs the "scheme" field was defined as mandatory. The current runtime implementation doesn't send a scheme in the allocation messages for hyperties and the Vertx node does not expect one. The current MN implementations are therefore not replacable. Please either change the implementations or the specs!