Re: Ajax via RSP/CGIDEV2

If one did gain knowledge of how it works (really works) that would be

great.

For an enterprise to blindly accept and implement an open source offering
(e.g. DOJO) without the knowledge of how it will affect their users
experience and how it will affect their web presence if something goes wrong
is just plain silly.  Sure the smaller the shop the more you can get away
with not digging in too deep before implementing.

But also understand that this is a new technology...

No it's not! The "Ajax" name is new (well, it's been well over a year, in

web-speak that's old) but the underlying technologies including the
XMLHTTPRequest object have been around for nearly a decade. 

Ok, now you are picking small points to fight about:-)  Some would say the
VOIP (Voice Over IP) is relatively new technology (guess maybe 4 years old)
but it is in fact more than double that.  I would still consider VOIP a new
technology because it was not able to be implemented in a widespread fashion
back in the mid 90's, but now it is fairly common and you see it all over TV
(I have a Vonage line and love it!)

In the same respects, sure the Javascript objects have been around for
awhile, and css and named tags have been around forever, but just because
you heard of it over a year ago and read some history on when it started
doesn't make it passé.  In my mind the only reason it is getting the
attention it has is BECAUSE it is now becoming industry compliant (say
browser compliant) which was the hold-up all along FWIU.

We're on the same team here Walden, just maybe not sitting on the same end
of the bench :-)

Later,
Aaron Bartell

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Walden H. Leverich
Sent: Thursday, June 22, 2006 11:46 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Ajax via RSP/CGIDEV2

and for a CGI programmer to have the knowledge of how the grears work 
under the covers is a great ace-in-your-pocket

If one did gain knowledge of how it works (really works) that would be
great. But, unless you're writing an internal app where you can dictate
IE-only, then do you really have knowledge of how to:

1) Create the XMLHTTPRequest object appropriately in all browsers
2) Handle multiple simultaneous requests if running Async? I've see lots of
code that will break if the second request starts before the first one ends.
3) Handle responses from the server w/return codes other than 200. 
4) Dispose of requests appropriately to handle memory leaks in IE.
5) Force "Connection: close" for Mozilla-based browsers which set the
content-length incorrectly on request
6) Handle cross-browser DOM and DHTML differences (eg. Firefox allows
innerHTML on TR and TD, IE doesn't)
7) etc.

And hey, I'm sure there are other problems that I don't know about.

But also understand that this is a new technology...

No it's not! The "Ajax" name is new (well, it's been well over a year, in
web-speak that's old) but the underlying technologies including the
XMLHTTPRequest object have been around for nearly a decade. 

-Walden

--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)

--
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.