title: Dagger2 one module for two different scopes
body: <p>In my app i have an ApplicationScope which provides me with stuff like context and shared prefs.
  2 sub components, LoggedInComponent and LoggedOutComponent.
  Those 2 subcomponents have other subcomponents which are less relevant to the issue.</p>
  
  <p>I have a NetworkModule which creates my retrofit instance.
  Both subcomponents need the NetworkModule but the retrofit might change during the login because the base url and other settings might change.</p>
  
  <p>I was wondering which approach it is better to take:
  1. Give both LoggedIn and LoggedOut sub components and the NetworkModule the same scope so both sub components can use this module. Feels a bit hacky and wrong usage of scopes.
  2. Put network module in the AppComponent with ApplicationScope. Also wrong usage of scope because network module is recreated so it cannot have same scope and also each recreation will cause the AppComponent and its subcomponents to be recreated.</p>
  
  <p>What would you do? maybe there is a better solution?</p>