Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

Namespace suggestions

by shotgunefx (Parson)
on Nov 17, 2005 at 22:10 UTC ( #509611=perlquestion: print w/ replies, xml ) Need Help??
shotgunefx has asked for the wisdom of the Perl Monks concerning the following question:

At the moment, I'm working on a package to control a Sanyo security vcr via RS-232C.

Not all controllable devices are VCRs, but it's all I'm interested in. The protocol is called SSSP (Sanyo Serial Security Protocol).

These devices can also be controlled by RS-485. I've got no plans on implementing that functionality.

I'd really like this to end up on CPAN when I'm done. Any suggestions for a namespace that makes sense giving the particulars?

Logically something like the following seems ok... but ugly.

Device::SSSP::VCR::Serial


-Lee

perl digital dash (in progress)

Comment on Namespace suggestions
Re: Namespace suggestions
by webfiend (Vicar) on Nov 17, 2005 at 22:56 UTC
    Your application is very narrow, so the namespace makes sense to me. It obviously describes a progressively more specific domain. It also leaves a lot of room for other modules which might fit somewhere else within that range. The name can't possibly be ugly if it correctly describes the purpose. Okay, maybe a name could be ugly, but I don't think that this is a valid example of ugliness.
      Thanks for the feedback. I don't think it's that bad, but something doesn't sit right about it. Perhaps it's because it's
      device::protocol::device::interface.

      Maybe Device::VCR::SSSP::Serial would be better.

      Perhaps I'm overthinking it.
Re: Namespace suggestions
by vaevictus (Pilgrim) on Nov 18, 2005 at 03:00 UTC

    is ::Serial necessary since SSSP is a Serial Protocol?
    or are you trying to insinuate that RS-232C is serial and rs-485 isn't? 485 is cool stuff too. :D

    so ... either drop the ::Serial or use ::RS232 or something.

      SSSP works via RS-232 and RJ-485. It's almost identical, except each has a few differing commands.
Re: Namespace suggestions
by kulls (Hermit) on Nov 18, 2005 at 04:27 UTC
    hi,
    If this module will only support "sanyo", then you can go ahead.but why don't you make this  Device::SSP::VCR::Serial (Serial Security Protocol) as separate family, so that in feature you can extend more vendors also right?
    -kulls
      I'm not sure if other companies use SSSP (or SSP, I've seen the third 'S' omitted) as a protocol.

      This particular module will be for VCRs, some of the command set I think carries over to the digital PVRs they now sell, but not 100% sure. But Sanyo definitely has other products that use it.

      The semantics of things like this always bug me. I would be surprised if there aren't other recorders with their own protocols. So figuring the right taxonomy is tricky. I think I'm starting to over think it. I'll throw a dart and pick one I guess.
Re: Namespace suggestions
by shotgunefx (Parson) on Nov 22, 2005 at 05:22 UTC
    Just about done. Still need to implement a few search commands, but about 95% there.

    Device::VCR::SSP::Serial

    Anyone know of the top of their head how to include additional files with ExtUtils::ModuleMaker?

    I have a sample vcr script I'd like to have picked up with the distro, but not installed anywhere outside of where the package is decompressed.

    Just so people can view it if they wish. What's the best way of including stuff like this?

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: perlquestion [id://509611]
Approved by ww
Front-paged by friedo
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (13)
As of 2014-09-23 17:38 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    How do you remember the number of days in each month?











    Results (234 votes), past polls