<div dir="ltr">Hello David, thanks for your response,<div class="gmail_extra"><br><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><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">On Thu, Jan 3, 2013 at 11:19 AM, Alexis Sukrieh <<a href="mailto:sukria@sukria.net">sukria@sukria.net</a>> wrote:<br>
><br>
> I don't get it. Do you have something that works (or is supported) in Dancer<br>
> 1 regarding session that is not in Dancer 2? If so, please enlight that, and<br>
> I'd be very happy to fix it.<br>
<br>
Look at the configuration values of Dancer::Session::Abstract. Are<br>
all supported in D2?<br>
<br>
Hint: ack for "session_name" in the D2 source tree, then ack for<br>
"dancer\.session".<br></blockquote><div><br></div><div style>Oh yes, you're right, I'll focus on this one as soon as I have time to go back to the code (hopefully this weekend).</div><div style> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Sessions happened to be the very first thing I was curious about in<br>
D2, given bugs I was finding in D1. Then I looked and found a big<br>
oversight like session configuration apparently unimplemented.<br></blockquote><div><br></div><div style>And I can tell you that the way sessions are handled in D2 are WAY better than in D1, exactly because of the experience I had with D1 bugs. I did a complete article in the advent calendar to stress how better it is now: <a href="http://advent.perldancer.org/2012/5">http://advent.perldancer.org/2012/5</a></div>
<div style><br></div><div style>I understand your point, you spotted one thing that I forgot, the configuration bits, it's being handled soon. That's my next todo item for D2. I've assigned the issue to myself.</div>
<div style><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
If I find that in the first place I look, should I expect similar<br>
oversights elsewhere? </blockquote><div><br></div><div style>I don't think so, although we should be honnest, D2 is younger than D1, of course, and yes, you're right, new software is less stable than old software. But my main point was that trying, or experimenting a D2 migration helps *a lot* D2 to move forward. See all the discussion that rose thanks to Celogeek's migraiton.</div>
<div style><br></div><div style>I was just saying that it could be a very good opportunity for you to contribute and help us make D2 more stable, if you want to.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Do I need to grok the entire architecture and<br>
do a code review to be sure? Maybe I was (un)lucky and found the one<br>
place that still has issues, but it's that kind of thing that makes me<br>
uncomfortable switching.<br></blockquote><div><br></div><div style>I don't think you should do a code-review, although I'd be very happy to have even more eyes on the code, as always. I think D2 is ready now for real-life tests, that's why I said that. Of course, that means beta-testing the monster, which requires some spare time and goodwill, of course ;)</div>
<div style> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Did I do a code review of D1? No. But then I expect that a large<br>
number of people using it for a few years have found the issues<br>
already. (Part of why I came to use Dancer is that it has already<br>
been well-established.) On the surface, D2 looks like D1, but it's<br>
such a re-write that I don't want to be a super-early-adopter and<br>
certainly not until the unimplemented sections I did find are fixed.<br>
<span class=""><font color="#888888"><br></font></span></blockquote><div><br></div><div style>I see your point of view, no problem ;)</div><div style><br></div><div style>Stay tuned, then.</div><div style><br></div><div style>
<br></div></div></div></div>