ajax

topic posted Wed, February 23, 2005 - 4:47 AM by  Zbigniew Luk...
Share/Save/Bookmark
Advertisement
An interesting article on all the new developments in java script and XMLHttpRequest based RIAs: www.adaptivepath.com/publica...0385.php

It is about how java script helps to make more asynchronous web applications by using XMLHttpRequest in the background.
Advertisement
Advertisement
  • Re: ajax

    Wed, February 23, 2005 - 2:23 PM
    Funny, I thought it was about slapping a $100,000 seminar on a technology from 1998.
    • Re: ajax

      Thu, February 24, 2005 - 3:36 AM
      Java script is not new, but how do you explain the fact that there were no apps like Google Maps or GMail before? Java script used to be hard to doo well - perhaps it was just gradual browser improvements plus knowlege about how to code it efficiently.
      • Re: ajax

        Thu, February 24, 2005 - 7:10 AM
        1) There have been plenty of apps built using the Google Maps and GMail methodologies. The first app I built using remote scripting functionalities similar to Gmail was in 2001, and relatively speaking, I was a latecomer. I found out about the technologies through simple web searching. Here, for example, is an Apple Developer connection article from a few years ago that I still have bookmarked:

        developer.apple.com/internet...rame.html

        I think this article dates back to 2002, and there are similar, even older articles on the O'Reilly site.

        2) Until recently, most work using these technologies has been in the corporate, behind-the-firewall, ASP(App Service Provider)-hosted, etc apps. This is because, while it's possible to build apps like this that work in Netscape 4, it's a pain in the ass. Corporate web-apps generally have far more controllable browser requirements. Microsoft's original remote-scripting technology worked cross-browser, but only if the server side was ASP(Active Server Pages). Ashley IT developed a bunch of ways around this, and I know these guys date back to 2001 at the latest:

        www.ashleyit.com/rs/main.htm

        3) The reason you're starting to see this technology used now in publicly accessable websites is largely thanks to standards advocates like Zeldman and WASP - Big companies like Google are finally dropping support for Netscape 4, which makes building apps like this a whole lot easier.
        • Re: ajax

          Thu, February 24, 2005 - 7:12 AM
          One more thing. Google has never used the term "Ajax" to describe any of their apps. That's the point I was making in my first post. An overrated "web-usability" firm slapped a name on an existing technology, and is somehow suggesting that they're responsible for it. That's just tacky.
          • Re: ajax

            Thu, February 24, 2005 - 1:56 PM
            I would agree with you on that. What they did was good stealth marketing I suppose.

            None the less, sometimes it takes someone to point out the obvious as is the case with Ajax for us to realize the possibilities.
            • Re: ajax

              Thu, February 24, 2005 - 3:02 PM
              Yeah, I took a step back after ranting about Ajax on a couple of places to re-examine the situation. For a very long time, the overrated and overpaid celebrities of the "user experience" world have been pretty disparaging of client-side scripting. Thanks to Google, Zeldman, and a few other web presences, this is now changing.

              If we can get the Adaptive Paths and the Nielsens of the world to embrace scripting, it makes those of us who understand these technologies a lot more marketable, especially to the "public" web. I don't think I'll ever be the type to get along with self-styled gurus of any type, but perhaps "Ajax" isn't such a bad thing after all.
              • Re: ajax

                Thu, February 24, 2005 - 4:41 PM
                hey guys,

                thanks for all of the enlightening posts.

                as a flash guy though im quizzical about google maps being in xhtml and javascript.

                i definitely see the advantage of strict xhtml/css etc in terms of having textual information on the web in a standards compliant format. but im confused as to why you should use it if you are going to jump through crazy hoops to get something to function like like google maps does.

                using the iframe to run the client seems a bit like a hack. and this stuff could obviously never be searched. can anyone clue me in?

                flickrs way of combining html and flash seems very on point to me. the content is for the most part html/css, but for the cooky stuff they use flash.

                isnt this the way to go?

                e.
                • Re: ajax

                  Fri, February 25, 2005 - 3:16 PM
                  Flash is fine but it still is overhead. If I can do it with the most minimal amount of overhead possible I will do it that way.

Recent topics in "Rich Internet Applications"

Topic Author Replies Last Post
Open-source versions of Flex and Air! Trevor 0 December 18, 2008
iScrybe.com? TantraTao 0 February 22, 2008
Hello - anyone around ?? Diana 0 February 24, 2007
Swicki Michael 0 November 17, 2006