I'm currently preparing the slides for my "Application deployment and dependency management with PAR" talk at YAPC::EU in Copenhagen.
There's a couple of things on my mind which I want to talk about. However, I realized that my view of what's important and/or interesting may be quite different from what other people think.
Hence, I'd like to give you the opportunity to tell me what you'd care about in the context of the suite of PAR modules. This way, I might get a somewhat better idea of what people other than myself would expect from a talk on the topic. Feel free to post a reply or send me an email (my PAUSE ID is SMUELLER).
Thanks for your input!
Steffen
This isn't exactly the feedback you asked for, so please feel free to disregard it. I like par for one file application upgrades. A friend of mine wrote a nice web framework that glues XML::Comma (he's the author of that module) and HTML::Mason together. There is a custom Mason resolver that looks to a PAR file for its components, and another chunk of logic that adds the "lib" directory of that PAR file to @INC.
This lets me scp a single PAR file to a server to upgrade an application, which I find super handy.
Good luck with your talk!
-- Douglas
