# Module refactoring and protocols

**URL:** <https://forum.elixirforum.com/t/module-refactoring-and-protocols/2227>\
**Category:** Questions\
**Tags:** protocols\
**Created:** [November 2, 2016, 11:20pm UTC](https://forum.elixirforum.com/t/module-refactoring-and-protocols/2227 "2016-11-02T23:20:39Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![bibekp](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/bibekp/32/3885_2.png) [@bibekp](https://forum.elixirforum.com/u/bibekp)\
**Post date:** [November 3, 2016, 3:25pm UTC](https://forum.elixirforum.com/t/module-refactoring-and-protocols/2227/4 "2016-11-03T15:25:02Z")

</div>

Thanks there @bbense.

I guess more than passing around different types I am more passing around modules – hence the use of behaviors.

This older [post](https://groups.google.com/forum/#!msg/elixir-lang-talk/Vq--xwBMmAI/WRjH3NKlZVYJ) helps to distinguish between the different types of polymorphic activity

My only minimal requirement would be for another module to abstract away the custom behaviors so my client code doesn’t need to worry about DominantStrategy vs. MixedStrategy

---

_[View the full topic](https://forum.elixirforum.com/t/module-refactoring-and-protocols/2227)._
