Hi Aaron

One final post from me on this, and it is not meant to be the last word,
simply to explain my position and opinion more clearly.

First any assertion or assumption that I 'dislike' the i or any part of it
is an error, and I apologise if my words have inferred that in any way. As I
have stated I have worked with the AS/400, iSeries, i for a long time (like
many others) and will continue to do so ( i am an avid supporter of IBM and
the i platform, and as I said own two machines myself).

I have also chosen some years ago to develop our web applications using
.NET, my preference that is all. Again I am not going to say (A) is better
than (B) or vice versa it just fits for me and the business solution we
provide. Since the i does not run .NET natively I develop my web apps on a
windows server (not unnaturally) and in my case this is an IBM xSeries.

The two machines talk nicely to each other through the IBM data provider and
it offers me great flexibility to develop either an iSeries web app, a SQL
Server Web App or one that talks to any other database. Accepted you can
also do this with PHP or practically any other language and the end result
will most likely be the same.

So why do I mention .NET in this group?, well granted it seems silly of me
since there is a whole list for that subject, but I do feel that a slight
segregation exists. .NET is web enabling the 400, I and many other people
use it for that, so why can we not discuss it in this list without entering
the 'Battle between Platforms' debate?

I expect we all enjoy our jobs as we are working with relatively new
technologies, so why can't we get on as a single unit with a single
direction (just 2 slightly different paths for getting there)?

I'll be more careful about jumping in non .NET threads in future, you were
right to pull me up on that, maybe a softer acceptance of other options by
you might help also.

Kind Regards

Maurice O'Prey













-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Aaron Bartell
Sent: 10 December 2010 22:26
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Why the IBM i *might* not be a good web server

This is a new vein you started, not me. You shouldn't make statements that
IBM i isn't fit to be a web server in a forum where many have had great
success with it if you want to eat your toast and beans in peace.

Currently I am eating my dinner ( beans on toast ). After I've eaten and
slept I may come back to you, although I do not see much point?

The point is that I don't think your reasons will be valid, though I usually
learn about the worst parts of IBM i the most from those that dislike
certain aspects of it.

I don't know why I am so full of piss and vinegar today, but backing down at
this point would be assimilation. So yes, please eat and rest so we can
have some good and fruitful discussion on the upsides and downsides of
Apache on IBM i vs. IIS on WindowsServer. I already know that Apache on IBM
i isn't without it's faults, but it is VERY capable of being a great web
server in my experiences. Maybe we just need to share experiences and that
will be enough?

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



On Fri, Dec 10, 2010 at 3:05 PM, Maurice O'Prey
<Maurice.Oprey@xxxxxxxxx>wrote:

Hi Aaron

I had hoped we had put this to bed ( or at least agreed to respect each
other's views ). Currently I am eating my dinner ( beans on toast ). After
I've eaten and slept I may come back to you, although I do not see much
point?

- Maurice



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.