On Mon, May 22, 2000 at 06:51:47PM +0530, Arun Kumar U wrote:
>    The following is the description of the package that I wish to
> contribute to CPAN. (I have already sent this desc. while registering for
> a CPAN id. My CPAN id is UARUN). 
>      
> 
> > Package: perlPOS
> > Description: A Set of Perl Modules that Implement ISO-8583 Protocol. This
> > modules is intended to provide the Perl Community with a financial
> > exchange/payment Framework. The iniital goal is to provide support for
> > client side applications to easily interface with ISO-8583 servers such as
> > ISO-8583 servers, switches etc. The package can also be modified to handle
> > ANSI X9.2 Protocol as well. 
> > 
> >    The inspiration for the package was derived from jPOS - A Java based
> > OpenSource library providing similar functionality. perlPOS is closely
> > modelled against the jPOS Project. The Home of the jPOS project is
> > at www.jpos.org [ . . . . ]
> 
>   perlPOS is implemented purly in Perl (no XS) and it consists of a
> number of packages (in the order of 25-30 packages). I am however a bit
> unsure about the namespace to choose. 
>     
>   I would like to use one of the following toplevel names
> 
>        a) POS::
>        b) perlPOS::  (or)
>        c) pPOS:: 
> 
>   Which one of the above should I use ?

    Of the three, I think that POS:: is best.  Everybody will know that it's
a Perl interface . . . .

    I was looking briefly at the jpos website, and I couldn't find what `POS'
stands for -- I'm assuming that it stands for `point of service', but it
doesn't seem to be an official protocol name.  I also wasn't sure what jpos
_does_, but it smells like it supports a network protocol.  Might I humbly
suggest Net::ISO8583?

    Peace,
* Kurt Starsinic ([EMAIL PROTECTED]) ---------- Senior Network Engineer *
|          `The term `Internet' has the meaning given that term in          |
|           section 230(f)(1) of the Communications Act of 1934.'           |
|           -- H.R. 3028, Trademark Cyberpiracy Prevention Act              |

Reply via email to