HAO LONG

Lightweight models and cost-effective scalability May 10, 2010

Once the idea of web services became au courant, large companies jumped into the fray with a complex web services stack designed to create highly reliable programming environments for distributed applications. But much as the web succeeded precisely because it overthrew much of hypertext theory, substituting a simple pragmatism for ideal design, RSS has become perhaps the single most widely deployed web service because of its simplicity, while the complex corporate web services stacks have yet to achieve wide deployment. Similarly, Amazon.com’s web services are provided in two forms: one adhering to the formalisms of the SOAP (Simple Object Access Protocol) web services stack, the other simply providing XML data over HTTP, in a lightweight approach sometimes referred to as REST (Representational State Transfer). While high value B2B connections (like those between Amazon and retail partners like ToysRUs) use the SOAP stack, Amazon reports that 95% of the usage is of the lightweight REST service. This same quest for simplicity can be seen in other “organic” web services. Google’s recent release of Google Maps is a case in point. Google Maps’ simple AJAX (Javascript and XML) interface was quickly decrypted by hackers, who then proceeded to remix the data into new services. Mapping-related web services had been available for some time from GIS vendors such as ESRI as well as from MapQuest and Microsoft MapPoint. But Google Maps set the world on fire because of its simplicity. While experimenting with any of the formal vendor-supported web services required a formal contract between the parties, the way Google Maps was implemented left the data for the taking, and hackers soon found ways to creatively re-use that data.

Leveraging the Long Tail May 5, 2010

The Long Tail

Small sites make up the bulk of the internet’s content; narrow niches make up the bulk of internet’s the possible applications. Therefore: Leverage customer-self service and algorithmic data management to reach out to the entire web, to the edges and not just the center, to the long tail and not just the head. A classic example of successful long tail sales is Amazon. A substantial subset of the book sales for the largest online retailer comes from obscure books. Amazon itself could afford to stock up on rare books as well as offer these via numerous online partners. The net effect is that a lot of book sales occured in the long tail. This phenomenon is captured nicely in a quote from an Amazon employee: “We sold more books today that didn’t sell at all yesterday than we sold today of all the books that did sell yesterday.” Like Google, DoubleClick is a true child of the internet era. It harnesses software as a service, has a core competency in data management, and, as noted above, was a pioneer in web services long before web services even had a name. However, DoubleClick was ultimately limited by its business model. It bought into the ’90s notion that the web was about publishing, not participation; that advertisers, not consumers, ought to call the shots; that size mattered, and that the internet was increasingly being dominated by the top websites as measured by MediaMetrix and other web ad scoring companies. As a result, DoubleClick proudly cites on its website “over 2000 successful implementations” of its software. Yahoo! Search Marketing (formerly Overture) and Google AdSense, by contrast, already serve hundreds of thousands of advertisers apiece. Overture and Google’s success came from an understanding of what Chris Anderson refers to as “the long tail,” the collective power of the small sites that make up the bulk of the web’s content. DoubleClick’s offerings require a formal sales contract, limiting their market to the few thousand largest websites. Overture and Google figured out how to enable ad placement on virtually any web page. What’s more, they eschewed publisher/ad-agency friendly advertising formats such as banner ads and popups in favor of minimally intrusive, context-sensitive, consumer-friendly text advertising. The Web 2.0 lesson: leverage customer-self service and algorithmic data management to reach out to the entire web, to the edges and not just the center, to the long tail and not just the head.

Perpetual Beta April 26, 2010

Release early and release often =? Perpetual BetaReal time monitoring of user behavior to see just which new features are used, and how they are used, thus becomes another required core competency. A web developer at a major online service remarked: “We put up two or three new features on some part of the site every day, and if users don’t adopt them, we take them down. If they like them, we roll them out to the entire site.” Every Beta need to test , even the new real one tool to show in the public before. It can bring many issues and negative influnce. We need solve these issues as soon as possible. If we can, the whole method and draft must to be good for the beta. Web 2.0 has been around for some time now and the buzz is finally starting to die down, at least amongst web professionals. One thing that doesn’t seem to be going away though is the Perpetual Beta  Every day I run across a new site that is in beta (and has been for a very long time), while not a huge problem and probably overlooked by many it is annoying. Some people may question why it even matters, but the reason why is because it’s nothing more than a diversion tactic.

Software above the level of a single device April 16, 2010

The PC is no longer the only access device for internet applications, and applications that are limited to a single device are less valuable than those that are connected. Therefore: Design your application from the get-go to integrate services across handheld devices, PCs, and internet servers. I think the device will reduce and the sofeware will increase, these two things opposite each other in the future. For instance, the blog and facebook allow us to update by using laptop or moblie phone. In this case, design a software which is run out of device. Or it could be the other devices. I mean the same software will be used in different devices but have the same function. This could be the better one for the future. It helps us save a lot of time and cost.

Rich user experiences March 27, 2010

the rich user experience is very significant to the web2.0 or applicantions. This is not only the web2.0′s duty, but also it is important to applications. These user experiences could help and engage many different applications or the company. Because it will get some negative feedbbacks and improve some innvoative ideas or changes after that. This is too much, helping and assisting web2.0 applications or tools. To achieve a target or goals, user experinence is more useful than other experiences. In addition, the rich experience could be more good for web2.0. Even the experience about negative, it also will help and assist the web2.0 to finish and improvement and to get the target. I know how the experience help the

Innovation in assembly March 20, 2010

Web2.0 which is relative to Web1.0 is a new class of Internet applications. The main features of Web1.0 is the users browser access to information. However, Web2.0 is more emphasis on the user’s interaction, the user is browsing web content, and also a maker of Web content. The web content producers are that every user on the Internet is no longer just the Internet, readers also become the author of the Internet, no longer just surfing on the Internet, but also a wave to the manufacturer, the model from a simple The read to write and build development, by passively receiving the Internet information to the initiative to create the development of Internet information, which is more humane! For instance, the blog is web2.0 application tool. Everyone can create blog which is belong to himself/herself. People design their blog’s style and post any information on the blog. Also other blog owners will comment each others. Some advice will be the best advantge benfit. The blog becomes a successful web2.0 tool.

Data is the next Intel Inside March 12, 2010

Data is a very significant information and knowledge which are frequently used for overlapping concepts. As we know, web2.0 describes data as the driving force behind applications. A Web 2.0 characteristic is data over the edge: unique, competitive, organized, fast, efficient and hard to recreate. “Data is the next Intel inside.” Therefore, data dominates the web2.0 and supports the web2.0 application. Now the data becomes the core which decides the most of web2.0. For instance, web2.0 application includes blogs. People could create the blog and update some new things in their blogs. Some times these information and messages are very useful and open others’ eyes. Thus, some good idea will be taken by company or other enterprise. This could bring many prices.

Harnessing Collective Intelligence March 8, 2010

A great product web2.0, full use of the collective wisdom, as long as you have heard above a certain amount of songs, it will recommend some taste similar to your users and artists, and you can enter an artist name on the radio channel to listen to all of last considered a similar style to the songs of the artist, you can also enter the song styles such as thrash metal, and then the radio will play the same type of songs. How easy way that could be!