One morning I wake up and see a pull request from a person I don't know on a project I haven't touched in years. Yup, it's a random contributor!
Yet another Dancer2 release hitting CPAN as we speak, all the way from Granada, Spain, courtesy of YAPC::EU 2015.
We've made a few interesting changes, highlights of which I would like to share with you.
In the previous post I discussed my January Pull Request Challenge contribution. It's only part 1 because there's another part: the contributions others made during their PRC which were related to projects I'm in charge of.
While I was focused on the social aspects of the PR Challenge, such as the IRC channel (opping literally everyone), the guides (wrote several), the repo (plus organization), and lately even a small parser for the web page Neil created (which will appear in another post), I still had my own responsibilities - mainly, my own PR challenge, and taking care of others' PR challenge contributions that fell under my purview.
On my quest for downloading more podcasts, I decided to tackle another podcast I started listening to, Criminal.
This posed a set of new problems, and I'm going to go over the code for solving it, since I'm actually somewhat proud of it.
I started getting into podcasts recently and one that I heard mentioned a few times was Welcome to Night Vale. I didn't get to listen to it yet, but decided I'll try it out.
When I start with a podcast, I want to download the episodes. I don't listen on my computer, I listen on my mp3 player. (Yes, I still havhttp://commonplacebooks.com/welcome-to-night-vale/e one, and no, it's not an iPod.)
At the same time, I'm sick of going over lists of pages, opening each, and then looking for the download button, so I wrote a Perl script that downloads all episodes for this podcast.
Gabor Szabo realized that it's very easy to dare me to do things and then making them available for Perl. I'm somewhat like Marty in Back to the Future - "I am not chicken!"
So, now we have LDTP. However, it needs your help. What is LDTP you ask? Good question!
Session affinity (also known as sticky sessions) is the ability to provide a user with a consistent backend from a reverse proxy, such as Perlbal. This is useful in case you cannot share the session data between backends, but do not want to lose the session.