comment on

You might be interested in reading about the P5EE project, which aims to come up with a standard solution for such things.

"Standard" being a relative term. TMTOWTDI, and as the project says, they aim to provide "one great way to do it."

As for how suitable Perl is, I can say that at work we've used Perl exclusively for implementing things such as a domain registrar system, and just about everything else we do.

Perl's suitability, like Java's, is largely a matter of perspective. I gather a lot of "suits" have been made to believe it must be Java for it to work, and I'm sure Java does have its advantages in certain situations. I'm fortunate not to work with any suits, so I have no first hand experience on that matter.

Other companies who maybe are more open-minded have had great success with Perl (i.e. Ticketmaster).

- Matt Riffle
VP Technology, pair Networks, Inc.
(although, I speak only for myself; code is untested unless otherwise stated)

In reply to Re: J2EE is too complicated - why not Perl? by mattriff
in thread J2EE is too complicated - why not Perl? by beamsack

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> <u> <ul>
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 intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


The stupid question is the question not asked
	PerlMonks