Hey all,
�
I am in the midst of building an "Yet Another Perl Application Server" package.� This is really a condensation of my experience and code thus far - ideally packaged so that others can use it as a basis for building their own apps.
�
At this point I am agonizing over what to call it and how to package it. Ideally I'd like to see it arrive in CPAN. I have a name I call my system. Actually I consider it two pieces - broken up in to 1/2 dozen modules. Some modules can stand on their own, some depend on others. It is open source, etc.
�
An example of what I've done is my own session handler. I used to use Apache::Session, but decided to write my own which is much faster and easier to use. Should I consider a name like Apache::Session::Lite? What about Session::Lite because it doesn't really have anything to do with Apache at all (Other than it is a good place to use it).
There has already been one extension of Apache::Session by Gerald Richter called Apache::SessionX. Just FYI. But also be sure to mention it in your SEE ALSO section.
�
What about my persistent object environment. Yes, yes, yet another one. I revied the others and they didn't work the way I wanted. Do I add this to Class::*? Or do I go the route of POE and create yet another top level name?
Why dont you discuss it on poop.sourceforge.net? And definitely it should be released separately.
Some guidance in the area would be most gratefully appreciated. I think I've got some good stuff here and would like to position it so that it gets the best possible reception!
O'Reilly has announced the call for papers for the Perl Conference.. YAPC::Na would be another place to discuss how these modules outdistance the pack.
