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.