Hi All,<div><br></div><div>   I&#39;m just starting with Dancer, pointers to applicable documentation are more than welcome if you don&#39;t have time to give an extended answer.</div><div><br></div><div>I sometimes am in the need of refactoring code that should be shared between different routes. As an example, I could have a POST route &#39;/do-operation&#39; that has to perform some operations and then generate a page exactly as if a GET route &#39;/default&#39; had been called.</div>

<div><br></div><div>I understand that it&#39;s not possible (not advisable) to call a route from another route, so the obvious solution that comes to mind is to create a function that encapsulates all that the &#39;/default&#39; route action is supposed to do, then call it from the two different routes:</div>

<div><br></div><div>sub default {</div><div>   # ...</div><div>}</div><div><br></div><div>get &#39;/default&#39; =&gt; \&amp;default;</div><div><br></div><div>post &#39;/do-operation&#39; =&gt; sub {</div><div>   # do whatever I need, then...</div>

<div>   return default();</div><div>}</div><div><br></div><div><br></div><div>Is this approach save and future-proof? In particular, what are the constraints of using the different Dancer functions - e.g. var, session, splat, ... - inside a sub that isn&#39;t &quot;installed&quot; as a route action in the way all the examples report?</div>

<div><br></div><div>To give a bit of perspective to my concern, I heard a lot about Devel::Declare and related stuff that plug in during the parsing phase, and I wouldn&#39;t like to incur in problems by not adhering to some &quot;best practice&quot;, whichever it is (e.g. use HTTP redirections to force the browser to send a new request for &#39;/default&#39;, but I would like to avoid this).</div>

<div><br></div><div>Thank you,</div><div><br></div><div>   Flavio.</div>