Création des Logiciels de gestion d'Entreprise, Création et référencement des sites web, Réseaux et Maintenance, Conception
Création des Logiciels de gestion d'Entreprise, Création et référencement des sites web, Réseaux et Maintenance, Conception
I recently gave a talk (preserved YouTube here) about the cache pattern and the Web Storage Portability Layer (WSPL) at Google I/O. It was exciting getting to give a talk at the Moscone Center as previously I had only ever been one of the audience members. The conference seemed to go by in a blur for me as I was sleep-deprived from getting the WSPL to "just good enough" to actually be released. (And some ofyou have already pointed out that I missed several bugs.) In my talk, I provided a general overview of the cache pattern and this post expands on the handling of hit determination and merging server and local changes.
The cache pattern is a design pattern for building an offline-capable web application. We implemented the cache pattern to make Gmail for Mobile tolerant of flaky wireless connections but the approach is generally applicable. Here's how it works. Consider a typical AJAX application. As shown in the diagram, we have a web application with a local model, view and controllers. The user interacts with theapplication and the controller dispatches XmlHttpRequests (XHRs for short) to the server. The server sends asynchronous requests to the application which it inserts into the model.
As shown in this next diagram, in the cache pattern, we insert a cache between the application and the server. Having done so, many requests that would otherwise require a round-trip to the network.
A software cache like this one shares a great deal conceptually with hardware caches. When designing the cache used in Gmail for mobile, we used this similarity to guide our design. For example, to keep our cache as simple as possible, we implemented a software equivalent to a write-through cache with early forwarding and LRU eviction. The cache pattern in general (and consequently our implementation) has four important data flows as shown in the diagram.
Webmasters have several ways to keep their sites' content out of Google's search results. Today, as promised, we're providing a way for websites to opt out of having their content that Google has crawled appear on Google Shopping, Advisor, Flights, Hotels, and Google+ Local search.
Webmasters can now choose this option through our Webmaster Tools, and crawled content currently being displayed on Shopping, Advisor, Flights, Hotels, or Google+ Local search pages will be removed within 30 days.
Posted by Matt Cutts, Distinguished Engineer
this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.comtext
and select
fields with common data types such as ‘full-name’ or ‘street-address’. With this attribute, web developers can drive conversions on their sites by marking their forms for auto-completion without changing the user interface or the backend.<input type=”text” name=”field1” x-autocompletetype=”email” />
x-autocompletetype
to indicate that this is still experimental and not yet a standard, similar to the webkitspeech
attribute we released last summer.<a href='URL-pemberi-komentar'>NAMA-pemberi-komentar</a>Dan jika seperti berikut maka blog tersebut belum Do Follow :
<a href='URL-pemberi-komentar' rel='nofollow'>NAMA-pemberi-komentar</a>Pemberian Backlink oleh blog Do Follow, hanya jika komentar diberi identitas Alamat/URL Blog. Namun jika dengan Akun Blogger, maka Backlink tidak akan sampai pada Blog, tetapi pada halaman Profil kita.2013, By: Seo Master
<dl id='comments-block'>Untuk masuk ke "Daftar Blog Do Follow" diatas, kawan-kawan hanya perlu melakukan penghilangan attribute rel="nofollow" pada kolom komentar saja.
<b:loop values='data:post.comments'var='comment'>
<dt class='comment-author'expr:id='"comment-" + data:comment.id'>
<a expr:name='"comment-" +data:comment.id'/>
<b:if cond='data:comment.authorUrl'>
<a expr:href='data:comment.authorUrl' rel='nofollow'><data:comment.author/></a>
<b:else/>
<data:comment.author/>
</b:if>
<data:commentPostedByMsg/>
</dt>
<b:includable id='backlinks' var='post'>2. Hapus kode rel='nofollow', lalu "save template". Selesai
<a name='links'/><h4><data:post.backlinksLabel/></h4>
<b:if cond='data:post.numBacklinks != 0'>
<dl class='comments-block' id='comments-block'>
<b:loop values='data:post.backlinks' var='backlink'>
<div class='collapsed-backlink backlink-control'>
<dt class='comment-title'>
<span class='backlink-toggle-zippy'> </span>
<a expr:href='data:backlink.url' rel='nofollow'><data:backlink.title/></a>
<b:include data='backlink' name='backlinkDeleteIcon'/>
</dt>
If you're a blogger (or a blog reader), you're painfully familiar with people who try to raise their own websites' search engine rankings by submitting linked blog comments like "Visit my discount pharmaceuticals site." This is called comment spam, we don't like it either, and we've been testing a new tag that blocks it. From now on, when Google sees the attribute (rel="nofollow") on hyperlinks, those links won't get any credit when we rank websites in our search results. This isn't a negative vote for the site where the comment was posted; it's just a way to make sure that spammers get no benefit from abusing public areas like blog comments, trackbacks, and referrer lists.Sejauh yang bisa kita pahami, jadi cuma satu alasan. Search Engine TIDAK menyukai SPAM, begitu pula kita. Ini adalah sebuah tindakan preventif yang bisa dilakukan untuk menghentikan usaha SPAMMING. Dengan adanya "tag" ini, seperti sudah sebut diatas, secara teknis, link menuju situs SPAM tersebut, tidak akan di"anggap" oleh Search Engine.
Após o registo de um domínio e criação de um site, a maioria dos webmasters quer ver o seu site indexado e aparecer nas primeiras posições no Google. Desde que iniciámos o suporte a webmasters de língua Portuguesa em 2006, vimos grande especulação acerca da forma como o Google indexa e avalia os sites. O mercado de língua Portuguesa, ainda numa fase de desenvolvimento em relação a SEO, é um dos maiores geradores de conteúdo na internet, por isso decidimos clarificar algumas das questões mais pertinentes.
Notámos como prática comum entre webmasters de língua Portuguesa a tendência para entrar em esquemas massivos de troca de links e a implementação de páginas única e exclusivamente para este fim, sem terem em consideração a qualidade dos links, a origem ou o impacto que estes terão nos seus sites a longo termo; outros temas populares englobam também uma preocupação excessiva com o PageRank ou a regularidade com que o Google acede aos seus sites.
Geralmente, o nosso conselho para quem pretende criar um site é começar por considerar aquilo que têm para oferecer antes de criar qualquer site ou blog. A receita para um site de sucesso é conteúdo original, onde os utilizadores possam encontrar informação de qualidade e actualizada correspondendo às suas necessidades.
Para clarificar alguns destes temas, compilámos algumas dicas para webmasters de língua Portuguesa:
Getting your site indexed
After registering a domain and creating a website, the next thing almost everybody wants is to get it indexed in Google and rank high. Since we started supporting webmasters in the Portuguese language market in 2006, we saw a growing speculation about how Google indexes and ranks websites. The Portuguese language market is one of the biggest web content generators and it's still in development regarding SEO, so we decided to shed some light into the main debated questions.
We have noticed that it is very popular among Portuguese webmasters to engage in massive link exchange schemes and to build partner pages exclusively for the sake of cross-linking, disregarding the quality of the links, the sources, and the long-term impact it will have on their sites; other popular issues involve an over-concern with PageRank and how often Google crawls their websites.
Generally, our advice is to consider what you have to offer, before you create your own website or blog. The recipe for a good and successful site is unique and original content where users find valuable and updated information corresponding to their needs.
To address some of these concerns, we have compiled some hints for Portuguese webmasters:
You should bear in mind that the process of indexing and how Google crawls your site includes many variables and in many cases your site won't come up as quickly in the SERPs as you expected. If you are not sure about some particular issue, consider visiting the Google Webmasters Guidelines or seek guidance in your community. In most cases you will get good advice and positive feedback from more experienced users. One of the recommended places to start is the Google discussion group for webmasters (in English) as well as the recently launched Portuguese discussion group for webmasters which we will monitor on a regular basis.
this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.comhttp://www.namablog.comPada intinya, identitas tersebut juga dijadikan sebagai Link/tautan ke alamat yang dimaksud. Yang kemudian dialih-bahasakan ke HTML menjadi :
<a href="http://www.namablog.com/">http://www.namablog.com</a>Pada dasarnya seluruh Link/Tautan ke alamat tertentu akan mempunyai format seperti diatas. Akan tetapi, pada system blog, baik wordpress, blogger(blogspot), blogsome atau yang lainnya format standard tersebut dengan sendirinya (oleh blogger disebut automagically) berubah menjadi :
<a rel="nofollow" href="http://www.namablog.com/">http://www.namablog.com</a>Apa yang berbeda? ya, yaitu munculnya attribute rel="nofollow".
Creative Commons image source. |