Much progress in the mod_parrot world. I spent the last week re-learning Parrot, since I really haven't touched it in a year, but I eventually got to coding a few days ago. My overall goal, btw, is to provide code that will serve as the basis for the parrot version of mod_perl (and other languages). And based on what I've seen this week, it can be done.
The original mod_parrot was limited by the Parrot API at the time, and only ran bytecode as a whole program, a la Apache::Registry. Nowadays we have goodies like namespaces and the ability to call Parrot subs from C (handlers!), making things much more interesting. This week I'm focusing on writing some internal wrappers for calling Parrot subs and the Apache module hooks. From there things are hazy, since there are so many directions I can go once I have an Apache module. I'll probably need to create a roadmap of sorts to keep my brain organized.
