Instead of keeping only a single 'active' transcoder, Session object now keeps a transcoder registry, i.e. a mapping from contract address to a corresponding transcoder. The new API:
the Session constructor takes no arguments
while deploying a contract you must pass a shared reference to a corresponding transcoder; in case of success, the new contract address will be internally connected with the transcoder
while calling a contract address, the corresponding transcoder will be looked up in the registry
for already deployed contracts, you can register their transcoders with set_transcoder or with_transcoder methods
Also, a minor refactor has been done: error and result types related to session have been moved to a submodule
Instead of keeping only a single 'active' transcoder,
Sessionobject now keeps a transcoder registry, i.e. a mapping from contract address to a corresponding transcoder. The new API:Sessionconstructor takes no argumentsset_transcoderorwith_transcodermethodsAlso, a minor refactor has been done: error and result types related to session have been moved to a submodule