<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2013/1/3 David Golden <span dir="ltr"><<a href="mailto:xdg@xdg.me" target="_blank">xdg@xdg.me</a>></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">
> Wouldn't that be a perfect opportunity to try a switch to Dancer 2?<br>
<br>
</div>I'm not planning on switching until the various session-related issues<br>
I opened are resolved. As I said in issue 126, config handling is<br>
opaque and seems to rely too much on hardcoded values.<br>
<br></blockquote><div style>Hmm, I'm surprised something that does not exist in Dancer 1 is a blocker for a D2 transition. Or maybe I miss something.</div><div style> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
These sorts of things are code smells and I think it's premature to<br>
encourage people to switch until those rough edges are sorted out.<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div style>I don't get it. Do you have something that works (or is supported) in Dancer 1 regarding session that is not in Dancer 2? If so, please enlight that, and I'd be very happy to fix it.</div>
<div style><br></div><div style>That doesn't mean the issue you're mentioning is interesting, and I'll take a look at what I can do (actually sessions are fare more better in D2 than in D1 if you look closely at the implementation).</div>
<div style><br></div><div style>Cheers,</div><div style><br></div></div></div></div>