quite some things were said about the how or why, mostly
on technical terms or money. Taking the viewpoint of a
salesperson (yuck!) I think three steps are required:
- Convince your customer that your technology (and
people) can do the job. Easily. Have done it before.
Many times. ;-)
For each of your points:
- Accept credit cards.
No prob, someone above pointed out perl examples.
- Manage user accounts.
No prob, we can interface with the OS user management
or implement our own.
- Serve information from databases.
DBI rulez (at least I never had probs getting what
I wanted from a database via DBI; let's you switch
databases if you want, just as JDBC). If I
remember correctly, btrott has deeper knowledge of
DBI, check his home node.
- Handle several XML interfaces to external systems.
Currently I am using XML::Parser and XML::XSLT with
_great_ success. Main problem may become
memory usage, but that
is inherent in the DOM specification, anyway, so
no different in Java.
- Point out at least one critical weakness in the
other approach. One might ask: how do I handle
many concurrent sessions without the need for a
very big (read: expensive) machine like IBM SP or
Sun E?k ?
- Make your offer (how much, how long).
Hope this helps ...
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.