#1172 Flatten the "transport" part

Open
opened 4 years ago by nero · 0 comments

Originally at 2015-04-10T20:42:50Z by Herbert Vojčík

Many pieces of Amber are now hardly dependent on the fact that modules are loaded via AMD, dependency lists are there etc. The existing "multi-trasport" is in fact not functioning, only one transport can de facto be used at a time.

Having been able to load / save packages using multiple different channels is nice to have, but actual implementation does not provide this and makes that part of code complicated.

Therefore I propose to flatten the hierarchies, hardcode just one way of exporting etc. to simplify the code and let the future implementors evolve it into multi-transport if they need to.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Originally at 2015-04-10T20:42:50Z by Herbert Vojčík Many pieces of Amber are now hardly dependent on the fact that modules are loaded via AMD, dependency lists are there etc. The existing "multi-trasport" is in fact not functioning, only one transport can de facto be used at a time. Having been able to load / save packages using multiple different channels is nice to have, but actual implementation does not provide this and makes that part of code complicated. Therefore I propose to flatten the hierarchies, hardcode just one way of exporting etc. to simplify the code and let the future implementors evolve it into multi-transport if they need to. <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/10881180-flatten-the-transport-part?utm_campaign=plugin&utm_content=tracker%2F79201&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F79201&utm_medium=issues&utm_source=github). </bountysource-plugin>
Sign in to join this conversation.
No Label
No Milestone
No assignee
1 Participants
Loading...
Cancel
Save
There is no content yet.