My First Interaction
This is my First IS696 class
This is my First IS696 class
Iam discussing about the History of Ajax :
The first use of the term in public was by Jesse James Garrett in February 2005. The term "Ajax" was coined in 2005 but Ajax start a decade earlier with Microsoft's initiatives in developing Remote Scripting. Techniques for the asynchronous loading of content on an existing Web page without requiring a full reload date back as far as the Iframe element type and the layer element type. Both element types had a src attribute that could take any external URL, and by loading a page containing JavaScript that manipulated the parent page, Ajax-like effects could be attained.
Microsoft's Remote Scripting acted as a more elegant replacement for these techniques, with data being pulled in by a Java applet with which the client side could communicate using JavaScript. This technique worked on both Internet Explorer version 4 and Netscape Navigator version 4 onwards. Microsoft then created the XMLHttpRequest object in Internet Explorer version 5 and first took advantage of these techniques using XMLHttpRequest in Outlook Web Access supplied with the Microsoft Exchange Server 2000 release.
More can be find in http://en.wikipedia.org/wiki/AJAX#History
The concept of "Web 2.0" began with a conference brainstorming session between O'Reilly and MediaLive International. Dale Dougherty, web pioneer and O'Reilly VP, noted that far from having "crashed", the web was more important than ever, with exciting new applications and sites popping up with surprising regularity. What's more, the companies that had survived the collapse seemed to have some things in common.
In the year and a half since, the term "Web 2.0" has clearly taken hold, with more than 9.5 million citations in Google. But there's still a huge amount of disagreement about just what Web 2.0 means, with some people decrying it as a meaningless marketing buzzword, and others accepting it as the new conventional wisdom.
Netscape was the standard bearer for Web 1.0, Google is most certainly the standard bearer for Web 2.0.Netscape framed "the web as platform" in terms of the old software paradigm: their flagship product was the web browser, a desktop application, and their strategy was to use their dominance in the browser market to establish a market for high-priced server products. Control over standards for displaying content and applications in the browser would, in theory, give Netscape the kind of market power enjoyed by Microsoft in the PC market. Much like the "horseless carriage" framed the automobile as an extension of the familiar, Netscape promoted a "webtop" to replace the desktop, and planned to populate that webtop with information updates and applets pushed to the webtop by information providers who would purchase Netscape servers.
Google, by contrast, began its life as a native web application, never sold or packaged, but delivered as a service, with customers paying, directly or indirectly, for the use of that service. None of the trappings of the old software industry are present. No scheduled software releases, just continuous improvement. No licensing or sale, just usage. No porting to different platforms so that customers can run the software on their own equipment, just a massively scalable collection of commodity PCs running open source operating systems plus homegrown applications and utilities that no one outside the company ever gets to see.
more can be find in http://www.oreillynet.com/pub/a/oreilly/tim/news/2005/09/30/what-is-web-20.html
Ajax technologies can be used in web applications providing many challenges for developers. There are numerous development groups working on USA government projects.
Web developers use Ajax in some instances to provide content only to specific portions of a web page, allowing data manipulation without incurring the cost of re-rendering the entire page in the web browser. Non-Ajax users would ideally continue to load and manipulate the whole page as a fallback, allowing the developers to preserve the experience of users in non-Ajax environments while giving those with capable browsers a much more responsive experience.
There is no doubt that AJAX and AJAX-style technologies are the way forward for web design. Developers can create true "applications" on the web like never before - however it needs to be taken with AJAX, in order to keep web sites secure.
One of the biggest threats, however, comes from the increase in complexity of Client Side scripting accompanied by the potential increase in the number of Server Side scripts used to make AJAX work. These scripts are "hidden from view" by the technology, making testing less intuitive - whilst at the same time the adoption of this new technology appears to make quite sane web developers forget the basics of good coding. Issues such as Access Control and Input Validation don't go away - they just multiply and become interwoven.
I have created new widgets and installed google reader widget but it doesn't show in my blog.Iam also ttrying to installed some more widgets which i have created but those widgets doesnot show in available list.Could anyone help me out!
Widgets will be one of the handiest link development tools of 2007. They have always been handy, but with the proliferation of bloggers, and common blog platforms, it makes the development of them that much more easy.There is a LOT of opportunity to build buzz and backlinks with widgets
An application programming interface (API) is a source code interface that a computer system or program library provides in order to support requests for services to be made of it by a computer program.An API differs from an application binary interface in that it is specified in terms of a programming language that can be compiled when an application is built, rather than an explicit low level description of how data is laid out in memory.
The software that provides the functionality described by an API is said to be an implementation of the API. The API itself is abstract, in that it specifies an interface and does not get involved with implementation details.
A well known API is the Single UNIX Specification.
An API is often a part of a software development kit (SDK).
There are various design models for APIs. Interfaces intended for the fastest execution often consist of sets of functions, procedures, variables and data structures. However, other models exist as well - such as the interpreter used to evaluate expressions in ECMAScript/JavaScript or in the abstraction layer - which relieve the programmer from needing to know how the functions of the API relate to the lower levels of abstraction. This makes it possible to redesign or improve the functions within the API without breaking code that relies on it.
Some APIs, such as the ones standard to an operating system, are implemented as separate code libraries that are distributed with the operating system. Others require software publishers to integrate the API functionality directly into the application. This forms another distinction in the examples above. Microsoft Windows APIs come with the operating system for anyone to use. Software for embedded systems such as video game consoles generally falls into the application-integrated category. While an official PlayStation API document may be interesting to read, it is of little use without its corresponding implementation, in the form of a separate library or software development kit.
The amount of information on the web is rapidly increasing. Google Reader helps me to keep up with it all by organizing and managing all the content interested in. Instead of continuously checking my favorite sites for updates, I can let Google Reader do it for me. From news sites to my friends' blogs, Google Reader helps me keep up-to-date with all the online information that matters most to me.
Service-oriented architecture (SOA) describes a software architecture that defines the use of loosely coupled software services to support the requirements of business processes and software users.
A service-oriented architecture is not tied to a specific technology. It may be implemented using a wide range of technologies, including REST, RPC, DCOM, CORBA or Web Services. The key is independent services with defined interfaces that can be called to perform their tasks in a standard way, without the service having foreknowledge of the calling application, and without the application having or needing knowledge of how the service actually performs its tasks.
SOA can also be regarded as a style of information systems architecture that enables the creation of applications that are built by combining loosely coupled and interoperable services. These services inter-operate based on a formal definition that is independent of the underlying platform and programming language. The interface definition hides the implementation of the language-specific service. SOA-based systems can therefore be independent of development technologies and platforms such as Java, .NET. Applications running on either platform can also consume services running on the other as Web services, which facilitates reuse.
SOA can support integration and consolidation activities within complex enterprise systems, but SOA does not specify or provide a methodology or framework for documenting capabilities or services.
more can be learned in http://en.wikipedia.org/wiki/Service-oriented_architecture
The vision of Web 2.0 in the enterprise is the user-defined experience and enhanced employee collaboration.RSS (Really Simple Syndication) was designed as an easy way to syndicate and deliver frequently updated information, like podcasts and news and blog feeds. It has since become the universally accepted way to deliver news and updates. Because RSS was designed for this purpose, its specification assumes that information feeds are publicly-available and unprotected. As such, the RSS specification incorporates no security mechanism whatsoever. Conversely, because of its wide-spread adoption, RSS has become a convenient way to deliver information not considered in the original RSS specifications.
more can be read in http://web2.sys-con.com/read/328021.htm
RSS (Really Simple Syndication) is a format for syndicating news and the content of news-like sites, including major news sites like Wired, news-oriented community sites like Slashdot, and personal weblogs. But it's not just for news. Pretty much anything that can be broken down into discrete items can be syndicated via RSS: the "recent changes" page of a wiki, a changelog of CVS checkins, even the revision history of a book. Once information about each item is in RSS format, an RSS-aware program can check the feed for changes and react to the changes in an appropriate way.
RSS-aware programs called news aggregators are popular in the weblogging community. Many weblogs make content available in RSS. A news aggregator can help to keep up with all our favorite weblogs by checking their RSS feeds and displaying new items from each of them.
more can be read in http://www.businessweek.com/search/rssfeed.htm
PHP is a widely-used general-purpose scripting language that is especially suited for Web development and can be embedded into HTML.
The PHP development team is proud to announce the immediate release of PHP 5.2.0. This release is a major improvement in the 5.X series, which includes a large number of new features, bug fixes and security enhancements.
Security Enhancements and Fixes can be read in:
http://www.php.net/releases/5_2_0.php
Software development changes can be found in:
http://www.php.net/ChangeLog-5.php#5.2.0