Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

What is the one-handed rule of WEB2.0?

2025-02-28 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Development >

Share

Shulou(Shulou.com)06/02 Report--

This article introduces what the one-handed rule of WEB2.0 is, the content is very detailed, interested friends can refer to it, I hope it can be helpful to you.

About WEB2.0. This noun should be no stranger to everyone. The Internet in China has been in an uproar in recent years, with some people praising it and some people thinking that it is hyped. But do all these people know about WEB2.0? Yes, I am targeting not only the C [X] O of various Internet companies, but also a number of bloger who want to stand out with a comment. Maybe people will think that I am such a person, so let's first take a look at what we now know about WEB2.0:

WEB2.0 is a concept that is not dominated by technology.

WEB2.0 is a general term represented by a series of websites.

WEB2.0 uses users as the source of content

WEB2.0 was written by Dell Doherty (Dale Dougherty), vice president of online publishing and research at O'Reilly Media Inc.

What I want to talk about here is the proposer and the company from here. Dale Dougherty is one of the first people to put forward API. For such a technical person to come up with a concept that is not dominated by technology, this alone can be regarded as an unbelievable hoax. Remember EMU said such a sentence: "A technical person with technical influence, once the work he is engaged in has lost its technical influence, it means that he has no influence." when there is no influence, any work he does will lose confidence and become ineffective. "

On the other hand, a series of websites are collectively referred to as representatives. Is that according to the model and structure of those sites is called the WEB2.0 era of the site? That's why there are so many "death-seeking WEB2.0". Because it is impossible to reach the so-called end point by describing multidirectional development from one end point.

Third, a lot of so-called content is king, and then there are users as the source of content. So where do our users come from? Does it mean that domestic companies except Tencent, Taobao and other companies with large user groups are unable to enter WEB2.0?

You can see that there are so many loopholes in the speech "What is WEB2.0" (officially designated translation) compiled by Tim O'Reilly, which is conveyed by the Chinese people. Just as no one in the page world does not know about a book, "website Reconstruction", it becomes DIV CSS in China. But you do not know if you have read this book seriously, there is such a sentence as Jeffrey Zeldman said, "that is, the extensive use of div tags as structural elements, not without fixed standards and reasons, but in fact this is a more advanced table abuse." The original text is "Well, if know anything about templates, you will know that you can use tables or tags. Well, it's the same for nested templates. In other words, if you wanted to yank out the tables and replace them with tags, you still can use nested templates and it will still work. There is no rule or technical reason that says you can't use tags in templates or nested templates or library items." So what really hinders our development is not the books of others that we "brought", but those ducks pinched by invisible hands written by Lu Xun.

However, this article is not just like many people just talk about his problems without solving him, that is, I want you to know the one-handed principle of WEB2.0. According to the second half of Tim O'Reilly 's presentation and Dale Dougherty's intention, we can sum up the technical merger congeners mentioned in the middle into the following 5 points in the order in which they appear in history (for example, the merger of RSS and XML into XHML, etc.):

API XHTML CSS AJAX SEO

Let's name the above five technical points according to the order of our fingers:

Let's all put one of our hands up again, just as you learned the Law of the right hand and the Rule of the left hand in physics class to do an experiment with me: (based on a normal human, of course) bend any finger separately to close to the palm of the hand, and see if the other four fingers are still in line with the back of the hand and comfortable. Have you noticed anything strange: when a single finger is bent, only the thumb [API] can complete the specified action.

Let's see what this means:

When a single technology is combined into implementation, only API alone can complete the task. However, API alone in our view should be only our users in the Internet, because these users will only continue to open source their own "interface" (not to mention the technical API here), and constantly output the materials and information we want, at the same time, our WEB2.0 can survive first on this point alone, that is, our common VC spending money. In such an era of WEB2.0, budding products are already very difficult; it is even more difficult to survive, and in a protracted war, they struggle in a survival stage but do not know how to use these technologies to maintain their own livelihood, and not being able to increase revenue and cut expenditure is tantamount to killing themselves.

To illustrate one by one, for example, the tail finger [SEO], that is, the common garbage station, does not have any technical skills to store as static pages, and how many garbage station owners will be forced to transform into server providers after being blocked by mobile. Then there is the ring finger [AJAX]. Here I would like to take the meal No as an example. They have made a bet with someone in the group before that they will not be able to last two years unless they are transformed. The reason why we are not optimistic about him is that we are unable to make the page static and the data static because of the excessive use of server operations; there will be too much traffic consumption and the performance consumption of the server spitting pages. When it comes to the middle finger [CSS], what is the corresponding form of WEB1.0 in the past? to develop a new terminal platform for a business, it is necessary to recruit a number of development teams. In the era of WEB2.0, we just need to use a development team and an excellent page refactorer to connect the media attribute of the CSS connection to "screen", "handheld", "TV" and so on to show different performance, so as to increase revenue and reduce expenditure.

Thus it can be seen that in WEB2.0, if you want to be truly invincible, you must bend five fingers together, that is, grasp five technologies together. Then many people will wonder that SEO and AJAX are in conflict with each other in terms of technology; so how can they co-exist in the field of WEB2.0 technology? Let's take a look at our hands. The ring finger [AJAX] and tail finger [SEO] are similar and connected. In our product form, this state only appears on our "Portal side" and "client side". We should do AJAX for the client side that users visit most (for the whole site), statically template and dynamically pull data. At the same time, we can also use the AJAX not to be included by search engines to protect users' unpublished, encrypted and peer-to-peer information and content. On the other hand, we should static the page file on the port side, so that the information that users want to publish is easier to be included by the search engine to increase the popularity of the site and users and gather the information. (this is about the information itself, not the users themselves, as many so-called WEB2.0 sites do today. Of course, there are a number of technical details here. On the other hand, it uses complete XHMTL (including semantic page files and RSS) to represent the page structure, and uses multi-directional CSS as a low-cost extension of multi-platform terminals. Finally, use multi-support plug-ins and standardized API (in this case, technical API) to nibble up those Internet territories that do not belong to you, such as Fanfu plug-ins (11 blog service providers), as well as confusing input channels (9) and API, which I think is very successful. Compared with other big brothers at present, they actually show a taste of "eating old money", such as blogcn, which lost power in "moving tools", and rampant input channels that have lost power. Wait.

This rule has been with me for almost a year. It has been in the way of looking at 3, doing 2 and saying 1, but this 3 has been done for almost a year; it is only now that I have not seen a higher 3 in my heart for the time being. However, I believe that "willing"-there is no need to give up, just as there is no 3 stage before I figured it out at the beginning. But the current situation really needs to be written about him. You can also see that the five technologies mentioned here are the responsibility of our website reconstructors (refers to website reconstruction rather than page reconstruction and page production), so we should have the responsibility and obligation to do a good job of WEB2.0 in China. Although we are only technical, the real WEB2.0 certainly has other aspects of assurance.

About what the one-handed rule of WEB2.0 is shared here, I hope that the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Development

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report