moritz_: the idea behind using a 204 response is so that the same mechanism can be used in the scripting and no-scripting cases (just a plain html form submit); also, it decouples sending a request from waiting for an answer to account for the cost of the frontend-controller-rakudo roundtrip and allow the script to produce all its output

moritz_: using visible session-ids would make it possible to pass links to them around: Bob has a problem, sends his session address to #perl6 and Alice can see excactly what Bob did and even show him how it's done correctly

moritz_: anyway, the first decision which should be made is to allow multiple sessions per client; if we don't, we can use cookies and the problem goes away; if we do, afaik it's either using a user-exposed session-id or breaking manual page-refresh

I'm giving a talk tomorrow about viv (and mentioning gimme5 and its history), and would like to focus in on cool Perl 5 things either in viv or Cursor.pm code, or cool things in the Perl 5 code it generates (such as STD.pmc)

pmichaud: you just *know* that even after all the care you've taken in slide #12, that the first question you're going to get at the end of the presentation is "So when will the official Perl 6 release be?"

mathw: I mean the difference between having the necessary basics to bind SSL and actually writing the bindings and having later something like SSL.pm The former is something rakudo would have to deliver, the latter isn't.

Is it kosher to say "multi infix:<eqv> (MyClass $a, MyClass $b) { ... }" or "multi infix:<cmp> (MyClass $a, MyClass $b) { ... }" in order to customize how, e.g., the series operator works? cmp() and eqv() are specced as multis, but so far as I can see, their infix equivalents aren't.

masak: Have you talked to the CPAN people like Dan Golden about doing that? There were some plans being thrown around for having *6/ folders for Perl 6, which would be handled by PAUSE. And in the CPAN 2.0 META spec you can set perl >=6.0 in the prereq spec

rakudo ad2afb: OUTPUT«Not enough positional parameters passed; got 1 but expected 2␤ in 'A::foo' at line 11:/tmp/Yk3oKm9kX1␤ in <anon> at line 844:CORE.setting␤ in main program body at line 11:/tmp/Yk3oKm9kX1␤»

my hacking time for tonight has run out. I have the beginnings of a pls proof-of-concept here, but I'll need another similar hacking session tomorrow to have something to publish. the half-time result looks satisfactory, though.