Commit Graph

4 Commits

Author SHA1 Message Date
Adrian Brink 125954ace8 Strongly typed transactions in handlers
During transaction processing we retrieve the type of msg and based on
that we get the applicable handler from the router. This means that the
router should only receive messages that it knows how to handle. Instead
of using Get interfaces, we should cast to the actual type of
transaction and then access the transaction details that way.
It's okay to panic here, because if the DummyHandler receives a message
that it cannot cast to the expected type it means something is wrong
with the router. Instead of retrieving an arbitrary key by chance we
should panic.
2018-02-17 16:51:20 -05:00
Jae Kwon b95b67d520 Separation of Tx from Msg; CodeType 2018-01-26 06:54:03 -08:00
Jae Kwon c6bad0b325 Add first Basecoin test harness 2018-01-26 06:54:03 -08:00
Jae Kwon 83f0ee31af
Split dummy into 2 files. (#371)
* Update examples/basecoin glide.lock
* Split dummy file
2018-01-24 01:04:44 -08:00