Quoth kemm...@nkcsd.k12.mo.us ("Kyle Emmons"):
> Hello module authors,
>
> I am preparing a new module for upload to CPAN. Currently it is named
> Net::PJLink, as it is an implementation of the PJLink network protocol
> (used for controlling multimedia projectors). However, I read the
> warning at
> https://pause.perl.org/pause/authenquery?ACTION=pause_namingmodules#Net
> and thought it would be best to make sure before requesting the
> namespace. Is there a more appropriate name for this module?
Seems like a good name to me. Is PJLink a sufficiently well-known name
for the protocol you're implementing that someone looking for this
module would search for that term?
> My second question concerns writing tests for this module. Most of the
> module's functionality is based on formatting and parsing network
> messages. I've thought of making the test fork a listener process that
> the tests can connect to, but I think that might cause problems on some
> platforms and firewalls.
I'd say this is right. If fork fails, or if you can't connect to the
listener and send a dummy message, skip the tests.
> I could put special functions in the module
> that would return the network message instead of sending it, but that
> wouldn't really be testing the network functionality.
In an ideal world you would do both, of course: test the functions that
do the protocol handling on their own, passing in strings, and then test
the network bits with a socket.
Ben
