in reply to Re3: Net::Server::POP3::Skeleton
in thread Net::Server::POP3::Skeleton
Though maybe not, since my module seems quite a bit more basic than yours, as it doesn't support any of the extensions and leaves a lot more up to the user to implement.
I'd probably have based my module on yours, if I'd
found yours on the CPAN when I was looking. That
might have influenced my interface. It might also
be that I wouldn't have been inspired then to put
mine on the CPAN, if yours was there already. Dunno.
I don't think I'll take mine down now, though, since
as you point out it implements more.
I'm curious, though, why you insist that your module is alpha. What necessesary features does it still lack?
It's alpha because it's less than three months old,
and I'm pretty much the only person working on it
(though I did get a one-line fix sent to me from a
person using the code once already). It's mostly
complete now, and I should probably graduate it to
beta status one of these releases. There are features
it still lacks. stopserver and restartserver
methods are lacking, and when I get those working
I'd like to augment the sample proxy with a control
script to start and stop it. APOP is not supported yet.
I still need to recheck RFC 1939 to make sure I've
implemented every MUST. It has been reported that
on some perls on some platforms $EOL needs to be
changed to "\r\n" to work correctly, but that breaks
it on Mandrake Linux (my development platform) and
I still need to figure out how to automatically
detect which way to go.
useful things that can be done without any of
these features, of course. Currently my development
is focusing mostly on the sample scripts and testing,
so I guess with the next release I could mark it beta.
split//,".rekcah lreP rehtona tsuJ";$\=$;[-1]->();print