Foundations of Ajax
We thought we had found the Holy Grail of software development when we started building Web applications several years ago. Previously we had been developing thick client applications that required a lengthy installation process every time a new version of the company’s application was released....
Đã lưu trong:
| Những tác giả chính: | , |
|---|---|
| Định dạng: | Sách |
| Ngôn ngữ: | English |
| Được phát hành: |
Apress
2012
|
| Những chủ đề: | |
| Truy cập trực tuyến: | https://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/31364 |
| Các nhãn: |
Thêm thẻ
Không có thẻ, Là người đầu tiên thẻ bản ghi này!
|
| Thư viện lưu trữ: | Thư viện Trường Đại học Đà Lạt |
|---|
| id |
oai:scholar.dlu.edu.vn:DLU123456789-31364 |
|---|---|
| record_format |
dspace |
| spelling |
oai:scholar.dlu.edu.vn:DLU123456789-313642014-01-20T06:15:05Z Foundations of Ajax Asleson, Ryan Schutta, Nathaniel T. Technologies We thought we had found the Holy Grail of software development when we started building Web applications several years ago. Previously we had been developing thick client applications that required a lengthy installation process every time a new version of the company’s application was released. The application was deployed to several hundred users scattered across the country, and much to our dismay we had to watch as the complex and error-prone installation process continually caused headaches and angst for developers and users alike. Deploying an application through a browser seemed like a much more palatable option because it would eliminate the need to install software on the client computer. So, like many others, our organization moved swiftly to deploying applications on the Web. Despite the relative ease of deployment, Web applications still had their share of issues. Most notable from a user’s perspective was the significant loss of rich interactivity provided by the user interface. Web applications were constrained to the basic set of widgets provided by HTML. Worse yet, interacting with the server required a complete refresh of the page, which was disconcerting to users who were familiar with rich client-server applications. We always considered this constant need to refresh the page a serious liability of Web applications and often experimented with ways to avoid a page refresh whenever possible; at one point, we even considered writing a Java applet that would handle the communication between the browser and the server. However, it soon became apparent that as more Web applications were deployed, users simply got used to the constant page refreshes, and our zeal for finding alternatives slowly faded. 2012-08-13T01:44:31Z 2012-08-13T01:44:31Z 2006 Book 1-59059-582-3 https://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/31364 en application/pdf Apress |
| institution |
Thư viện Trường Đại học Đà Lạt |
| collection |
Thư viện số |
| language |
English |
| topic |
Technologies |
| spellingShingle |
Technologies Asleson, Ryan Schutta, Nathaniel T. Foundations of Ajax |
| description |
We thought we had found the Holy Grail of software development when we started building
Web applications several years ago. Previously we had been developing thick client applications
that required a lengthy installation process every time a new version of the company’s
application was released. The application was deployed to several hundred users scattered
across the country, and much to our dismay we had to watch as the complex and error-prone
installation process continually caused headaches and angst for developers and users alike.
Deploying an application through a browser seemed like a much more palatable option
because it would eliminate the need to install software on the client computer. So, like many
others, our organization moved swiftly to deploying applications on the Web.
Despite the relative ease of deployment, Web applications still had their share of issues.
Most notable from a user’s perspective was the significant loss of rich interactivity provided
by the user interface. Web applications were constrained to the basic set of widgets provided
by HTML. Worse yet, interacting with the server required a complete refresh of the page,
which was disconcerting to users who were familiar with rich client-server applications.
We always considered this constant need to refresh the page a serious liability of Web
applications and often experimented with ways to avoid a page refresh whenever possible;
at one point, we even considered writing a Java applet that would handle the communication
between the browser and the server. However, it soon became apparent that as more Web
applications were deployed, users simply got used to the constant page refreshes, and our
zeal for finding alternatives slowly faded. |
| format |
Book |
| author |
Asleson, Ryan Schutta, Nathaniel T. |
| author_facet |
Asleson, Ryan Schutta, Nathaniel T. |
| author_sort |
Asleson, Ryan |
| title |
Foundations of Ajax |
| title_short |
Foundations of Ajax |
| title_full |
Foundations of Ajax |
| title_fullStr |
Foundations of Ajax |
| title_full_unstemmed |
Foundations of Ajax |
| title_sort |
foundations of ajax |
| publisher |
Apress |
| publishDate |
2012 |
| url |
https://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/31364 |
| _version_ |
1819781607489273856 |