title: How can I ensure orleans grain consistency?
body: <p>In erlang you can pass initial state to actor when spawning it. This way you don't need to deal with init messages which take actor to it's initial state again or messages needing init message arrived before. In orleans given the assumption of grains always exist you can not use constructors. Is there any way to pass initial state to grains, avoiding thus any init method which break consistency by needing it to be called before any other method?</p>
  
  <p>When I say "take actor to it's initial state", I mean, in orleans context, call init method of specific grain activation twice. It is like overwriting state. May be you need this king of message which reset state but if you don't need it,  it is a pitfall, a potential source of bugs.</p>
  
  <p>I'm looking for some type of constructor, something like <code>spawn(module, function, [initial state])</code> from erlang. My first attempt was look for any overload of GetGrain with the following signature: <code>GrainFactory.GetGrain&lt;IGrain&gt;(id, initialState);</code></p>