suedunnell wrote: Hi Again - I should add my name to comment #1 above and ask that if anyone has questions, they can either post them here or ask me directly:
Sue Dunnell
PowerBuilder Product Manager
978 287 1752
sue.dunnell@sybase.com
I just read SYS-CON's response to the recent attacks in Fuat Kircaali's Social Media Terrorists blog entry. I realized the email quoted at the end of Kircaali's blog was also copied to Ted Weissman of Lois Paul & Partners, a public relations firm with clients in technology.
If this email was sen...
Asynchronous Java Script and XML, shortened to Ajax , is the flared technology de-jour. Like fashion, cooking, or music it’s a mix of stuff that’s old, borrowed, and not that new. It does exactly what it says on the tin, mixing Java Script on the browser with async XML traffic.
The problem with the web has always been that despite anyone trying to convince you otherwise, it’s a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don’t have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power. Java Script has always been a sensible way to try to reduce server round trips where client side validation or other logic can be performed, and also to butter up the GUI with dialogs and other user interface experiences above the lowest common denominator of HTML. The latency problem however has typically remained where each page’s unit of work is completed by despatching a request to the server with the data and a new page dispatched. What makes Ajax clever though is that it keeps the HTTP transaction alive and uses it to perform fine grained requests during the lifetime of the page, and doing this asynchronously by having the browser’s Java Script communicate with the server doesn’t detract from the client’s responsiveness. It also removes the whole web experience feeling where waiting for the result of an HTTP communication is usually coincident with having to wait for a new page and the whole experience goes into a synchronous busy wait.
What makes Ajax so cool all of a sudden isn’t the idea underlying it strengths, these have been around for ages, it’s basically that Google maps uses it. This allows a very crisp experience scrolling through maps that is just vastly superior to the tradition technique of “click the scroll left button and wait for a whole new synchronous new page to be give to you”.
Technology never wins because it’s the best – it’s because it gets market and mind share. Windows was a poor technology when it competed and won with superior operating systems like OS/2 and Mac because it had more and cheaper apps available on it. VHS beat Betamax because the tapes were larger and could fit more stuff on them despite poorer picture quality. What Ajax has going for it in this vein, is that no plugin is required in the browser -just Java Script meaning that anyone with even the most basic of web browsers can run an Ajax app without having to ensure the right client plugin level exists for their platform.
Ajax has the feel of being a big upstart in the client stage. Rather like teenagers fretting over the fact that their peers are having more fun and wilder parties they clamour to get invited to, to those who haven’t done Ajax it has mystique and allure because Google use it. and they are cool Big waves come from small tipping points. Like technologies that win Ajax is simple, elegant, and a combination of old ideas and techniques packaged together with shiny paper and a cool reference account. Will it become the client server bundling that wins over all of the myriad of alternatives flapping in the same weather system. I think yes, and I think it is very important to back, not because in five years time I think the choice will be Ajax or Longhorn, but because Ajax makes client server work and offers a rich user interface experience. It could yet be the holy grail of client server.
About Joe Winchester Joe Winchester, Editor-in-Chief of Java Developer's Journal, was formerly JDJ's longtime Desktop Technologies Editor and is a software developer working on development tools for IBM in Hursley, UK.
Reader Feedback: Page 1 of 1
#6
SYS-CON Australia News Desk commented on 27 Jun 2006
The problem with the web has always been that despite anyone trying to convince you otherwise, it's a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don't have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.
#5
SYS-CON Italy News Desk commented on 27 Jun 2006
The problem with the web has always been that despite anyone trying to convince you otherwise, it's a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don't have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.
#4
AJAXWorld News Desk commented on 27 Jun 2006
The problem with the web has always been that despite anyone trying to convince you otherwise, it's a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don't have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.
#3
SYS-CON India News Desk commented on 11 Apr 2006
The problem with the web has always been that despite anyone trying to convince you otherwise, it's a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don't have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.
#2
AJAX News Desk commented on 11 Apr 2006
The problem with the web has always been that despite anyone trying to convince you otherwise, it's a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don't have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.
#1
JDJ News Desk commented on 15 Dec 2005
Joe Winchester's Java Blog: Rich Client, Poor Client, Cool Client, AJAX. The problem with the web has always been that despite anyone trying to convince you otherwise, it's a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don't have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.
SYS-CON Australia News Desk wrote: The problem with the web has always been that despite anyone trying to convince you otherwise, it's a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don't have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.
SYS-CON Italy News Desk wrote: The problem with the web has always been that despite anyone trying to convince you otherwise, it's a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don't have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.
AJAXWorld News Desk wrote: The problem with the web has always been that despite anyone trying to convince you otherwise, it's a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don't have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.
SYS-CON India News Desk wrote: The problem with the web has always been that despite anyone trying to convince you otherwise, it's a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don't have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.
AJAX News Desk wrote: The problem with the web has always been that despite anyone trying to convince you otherwise, it's a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don't have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.
JDJ News Desk wrote: Joe Winchester's Java Blog: Rich Client, Poor Client, Cool Client, AJAX. The problem with the web has always been that despite anyone trying to convince you otherwise, it's a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don't have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.
Want to know what gets my blood pressure up? It’s when there’s both a huge shift in thinking around how we should do computing, namely cloud computing, and at the same time, there’s a bunch of information out there that causes confusion. As cloud computing hype spikes to a frenzy, so d...
"What's fueling the interest in RIA?" asked Regev Yativ, President & CEO of Magic Software Enterprises in the Americas, at the beginning of his session at AJAX World RIA Conference & Expo in NYC last month. The answer is the growth of broadband, Yativ said, which has made the Internet ...
System architects and engineering teams are designing increasingly complex embedded systems in order to satisfy their customers’ stringent functionality and performance requirements. In addition, within tactical systems, it’s not uncommon to require deterministic real-time behavior whi...
With the spoils of the BEA acquisition now fully baked into the mix -- and with anticipation for what the pending Sun Microsystems buy brings -- Oracle is well on its way to obviating the middleware moniker. Perhaps we should call it "anyware."
Oracle has announced the general availability of Oracle Service-Oriented Architecture (SOA) Suite 11g, which helps customers and partners to lower costs, improve efficiencies and increase visibility into their businesses and operations. This next-generation business application infrast...
As part of today's Oracle(R) Fusion Middleware 11g launch, Oracle announced that Oracle Fusion Middleware remains the Company's fastest growing business. Oracle's commitment to delivering innovative products strengthened Oracle Fusion Middleware's position as an industry leader in vend...
About Newsfeeds / Video Feeds
.gif)
Want to know what gets my blood pressure up? It’s when there’s both a huge shift in thinking around how we should do computing, namely cloud computing, and at the same time, there’s a bunch of information out there that causes confusion. As cloud computing hype spikes to a frenzy, so d...
"What's fueling the interest in RIA?" asked Regev Yativ, President & CEO of Magic Software Enterprises in the Americas, at the beginning of his session at AJAX World RIA Conference & Expo in NYC last month. The answer is the growth of broadband, Yativ said, which has made the Internet ...
System architects and engineering teams are designing increasingly complex embedded systems in order to satisfy their customers’ stringent functionality and performance requirements. In addition, within tactical systems, it’s not uncommon to require deterministic real-time behavior whi...
With the spoils of the BEA acquisition now fully baked into the mix -- and with anticipation for what the pending Sun Microsystems buy brings -- Oracle is well on its way to obviating the middleware moniker. Perhaps we should call it "anyware."
Oracle has announced the general availability of Oracle Service-Oriented Architecture (SOA) Suite 11g, which helps customers and partners to lower costs, improve efficiencies and increase visibility into their businesses and operations. This next-generation business application infrast...
As part of today's Oracle(R) Fusion Middleware 11g launch, Oracle announced that Oracle Fusion Middleware remains the Company's fastest growing business. Oracle's commitment to delivering innovative products strengthened Oracle Fusion Middleware's position as an industry leader in vend...
