:: A.M.D. :: Bildiri :: Forum :: Üyelik :: Webshop :: İletişim :: Yönetici Alanı ::
  Hoşgeldin Ziyaretçi Üye Ol

   Üye Girişi


Kullanıcı Girişi

Üye Adı:
Şifre:

[ Üye Ol ]


   Menü

  

   Marşımız




  
Yorumlar yazarlarına aittir. İçeriklerinden biz sorumlu tutulamayız.

kWLoCtuXKC (Puan: 0)
Gönderen: Misafir Tarih: 14.09.2013 Saat: 05:55
I think the issue here is the need to identify not only the bworser, but also the device. UAProf's have this ability, (especially with the diff header), but haven't seen very good adoption.Most user agents in the web world already indicate both the bworser and the OS.What is to stop the User-Agent being an extended form of something like:Mozilla/5.0 (SonyEricssonK800i/R1JC)This, along with suitable accept headers indicating supported content types that would be passed through directly to the native bworser (Like OMA mime types) would be a clean solution? It identifies the bworser to allow the site to select an appropriate rendering, but also indicates the device keeping people needing to target content at specific handsets happy.Some of the earlier Opera Mini releases I saw presented the underlying device as part of the user-agent, but this seemed to be phased out later on, which is a pity in my opinion.The disadvantage of using headers other than the user-agent and other common ones (accept header for example) to tailor the presentation, is that most proxies are very flaky with properly handling the vary header for caching except when used with common headers.Steve


[ Cevap Ver | Yukarı ]

Copyright (c) - A.M.D. - Tüm hakları saklıdır. - Malatyasporum.com

Bir Dizayncini.com yapımıdır