On Aug 23, 11:08 am, shamus <[EMAIL PROTECTED]> wrote:
> Thanks to everyone for their feedback.
>
> Let me rephrase the question here a bit. For example, say I would like
> to serve a different webpage to visitors using 1.1.4 vs 2.0. Obviously
> UA detection is not the best solution to detect them, so how would you
> suggest to accomplish this?
The answer depends on why you want to do that.
On the web it is assumed that visitors will be using a wide variety of
browsers and platforms. Since this is a group dedicated to web
applications (and hence primarily HTML, CSS and javascript) I take the
view that a web application should support as many of those visitors
as is reasonable. Browser detection is a poor strategy to do that
(don't take my word for it, do a search).
If you don't know if a visitor's browser supports a certain feature,
test for it and provide a reasonable fallback, then you don't care
what the UA string is. If lack of support for a feature is fatal to
your application, at least you can say "This page requires support for
<blah>, your browser doesn't seem to support that".
On the other hand, if you are developing an application that is solely
for iPhone users, then go right ahead and sniff the UA string all you
like, but even there feature detection will be a useful strategy
unless you are prepared to write different versions of HTML, CSS or
script for each version to be supported.
Without knowing why you want to know the difference (e.g. the specific
feature of v2 that is missing in v1), all that can be provided is
general advice as above.
--
Rob
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"iPhoneWebDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/iphonewebdev?hl=en
-~----------~----~----~----~------~----~------~--~---
