Re: The ASF Resigns From the JCP Executive Committee

So does that mean I have to stop the server and restart it? I wouldn't
think that is an acceptable practice in a production environment.

Also, do you have a link you can point me to that describes this? Note I am
very familiar with debugging with the server when the server is on my PC
(works excellently). It's when the server is a separate production machine
that I haven't seen seamless ways to do server side debugging.

Aaron Bartell
www.MowYourLawn.com/blog
www.OpenRPGUI.com
www.SoftwareSavesLives.com



On Tue, Dec 14, 2010 at 8:48 AM, <TAllen@xxxxxxxxxxxx> wrote:

Aaron,

Server side debugging could not be any easier with Java in Eclipse or
Rational/Websphere Studio. Simply start the server is debug mode, set your
breakpoints and off you go.
(I hope I have not misunderstood what you were saying below.)

Thanks,
Todd Allen
EDPS
Electronic Data Processing Services
tallen@xxxxxxxxxxxx




Aaron Bartell
<aaronbartell@gma
il.com> To
Sent by: "Web Enabling the AS400 / iSeries"
web400-bounces@mi <web400@xxxxxxxxxxxx>
drange.com cc

Subject
2010-12-14 09:06 Re: [WEB400] The ASF Resigns From
the JCP Executive Committee

Please respond to
Web Enabling the
AS400 / iSeries
<web400@midrange.
com>






What are the primary reasons you consider PHP not enterprise ready?

It's not that I don't like Java or PHP, but there are things I prefer in
the
RPG stack. For example, server-side step-thru debugging is just easier to
me with RPG. I am not even sure if it can be done yet in Java, but I know
that PHP has something (though I haven't tried it lately, so it is probably
better than it was a few years back when I tried it).

I think the main issue I have with somebody calling something enterprise
ready or not is that many times it is relative. For example, you can run
an
enterprise on .NET if you add enough failsafes. The same is true for any
language, including RPG - some stacks just require less failsafes.

So it is obvious that PHP *can* be run in an enterprise environment, but
what are the things that cause PHP in the enterprise to leave a bad taste
in
your mouth. Or rather, what should they fix before you would pursue it.

On the other note that is floating around in this thread - I am in the camp
that don't consider Java that hard - though I steer clear from many of the
more complex areas of the language and many times consider myself a
"modular
Java programmer". I think it is more that there are so many things to
learn
vs. the concepts being hard. Coming from RPG, we just didn't have to be
mindful of very many things. Database connection pool - what's that? :-)

Aaron Bartell
www.MowYourLawn.com/blog
www.OpenRPGUI.com
www.SoftwareSavesLives.com



On Tue, Dec 14, 2010 at 6:12 AM, Joe Pluta
<joepluta@xxxxxxxxxxxxxxxxx>wrote:

On 12/14/2010 12:16 AM, Mike Pavlak wrote:

Well, Joe, we'll have to agree to disagree. I see PHP as a VERY

Enterprise oriented language.

I'm not sure how many enterprise applications you've designed, Mike, but
PHP is not a language I'd use to write any business logic in. If you
recommend it for, say, MRP processing, then you are either very, very
wrong or a salesman. PHP as a front end to RPG, perhaps, but then
you've learned two languages to do one thing: present business logic to
the web. Anyway, we've been over this ground already. We all know you
work for Zend and everybody knows what I advocate, so our opinions are
already pretty much Open Source. :)

This communication and any transmitted documents are intended to be
confidential. If there is a problem with this transmission, please contact
the sender. If the reader of this message is not the intended recipient, or
the employee or agent responsible to deliver it to the intended recipient,
you are hereby notified that any dissemination, distribution or copying of
this communication is strictly prohibited.

--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.