Re: Theory behind ASP.NET mobile device capabilities?

From: JuanDG (jdgx_at_hotmail.com)
Date: 09/23/04

  • Next message: Sara T.: "Problem with render page to html" 
    Date: Thu, 23 Sep 2004 15:03:23 -0500

    We'll I thought at first this was some kind of beginner question, but I see
    you want "the real thing!!", so here I come!!

    Microsoft has it's own implementation of the Device Capabilities assessment
    written in the ASP.NET Engine (HTTP Pipelines) this pipelines are a
    collection of HTTP modules

    HTTP modules are classes that have access to the incoming request. These
    modules can inspect the incoming request and make decisions that affect the
    internal flow of the request. After passing through the specified HTTP
    modules, the request reaches an HTTP handler, whose job it is to generate
    the output that will be sent back to the requesting browser. all the
    information about the mobile device capabilities is written in the request.

    In fact, you can see a precise list of what modules are used by default by
    going to the machine.config file (located in the
    $WINDOWS$\Microsoft.NET\Framework\$VERSION$\CONFIG directory). Fist you can
    search for an element called <sectionGroup name="system.web"> and then the
    section corresponding to the devicefilters (<section name="deviceFilters"
    type="System.Web.Mobile.......). And the mobile controls (<section
    name="mobileControls" type="System.Web.UI.MobileControls...) they are the
    main classes for mobile web development in asp.net and as you can see they
    are in charged of handling requests from mobile devices.

    You'll also find a <mobileControls> tag and after this tag you'll locate al
    the device filters and if you have installed device updates you'll see the
    changes made by them in this section. This is the most interesting part
    because you'll meet the actual classes who take care of the rendering, like
    System.Web.UI.MobileControls.Adapters.WmlTextBoxAdapter capable of rendering
    textboxes to WML and a whole bunch of them for all the devices supported by
    the framework.

    then there's the <browserCaps> tag where you'll find all the set of
    capabilities ASP.NET defines for each type of browser it supports, as you'll
    see it's some what similar to WURFL and also very plain and simple.

    You can keep browsing the machine.config and the whole config folder and at
    the end you'll get the picture of how all the dirty work is done!!!!

    Hope its all clear now. Cheers!!! 

    --
Juan David Gomez A.
Microsoft Certified Professional
Analista de Desarrollo - PSL S.A.
Web and Wireless Banking
Medellin - Colombia
"bonnie" <bonnieliyl@postmaster.co.uk> wrote in message 
news:a0003953.0409222342.5d558e76@posting.google.com...
> Hi Juan,
>
> Thank you very much for the reply.
>
> I have watched the animation before and now once again. It explains
> well what the whole picture is like and how it works. But what I was
> looking for is how Microsoft realize recognizing device capabilities
> and filtering devices. W3C has made a standard, called Composite
> Capabilities/Preference Profile(CC/PP), a framework for expressing
> device capabilities and user preferences. OMA, former WAP Forum, has
> developed its own implementation for WAP devices based on this,
> UAProf. It defines an extensible vocabulary, and a protocol
> transforming the profiles as well. There are some OpenSource projects
> implementing CC/PP, such as DELI
> (http://www-uk.hpl.hp.com/people/marbut/). Also some people are
> implenting their own mechanism, such as WURFL
> (http://wurfl.sourceforge.net/index.php).
>
> But how does Microsoft's work? Does it have its own mechanism or it
> follows some standard too? I can't find where to find such
> information.
>
> BR, Bonnie
>
> "JuanDG" <jdgx@hotmail.com> wrote in message 
> news:<OE67EqBoEHA.648@tk2msftngp13.phx.gbl>...
>> Maybe this animation can be helpful
>> http://www.asp.net/mobile/flasharchitecture.aspx?tabindex=6
>>
>> --
>>
>> Juan David Gomez A.
>> Microsoft Certified Professional
>> Analista de Desarrollo - PSL S.A.
>> Web and Wireless Banking
>> Medellin - Colombia
>>
>> "bonnie" <bonnieliyl@postmaster.co.uk> wrote in message
>> news:a0003953.0409150242.1f30534@posting.google.com...
>> > Hi,
>> >
>> > Is there anyone who knows the theory behind mobile capabilities of
>> > mobile ASP.NET? Has it anything to do with CC/PP, UAProf, or any other
>> > standards? Where should I find this information? Thanks for any
>> > replies.
>> >
>> > bonnie
  • Next message: Sara T.: "Problem with render page to html"

    Relevant Pages

    • I got a response from Microsoft Permission/Copyright group regarding masm
      ... I explicitly requested commercial use permission. ... request are listed below for reference. ... Company agrees to be bound by the terms of the attached Microsoft ... MASM32 software package. ...
      (alt.lang.asm)
    • Re: how can we restrict what certificate WSE will use?
      ... \par Microsoft Online Support ... \par you mentioned 'since his private key is not valid so, the signature of his ... \par in a request signed with his valid private key, and since his public key is ...
      (microsoft.public.dotnet.framework.webservices.enhancements)
    • RE: No one knows?
      ... © 2001 Microsoft Corporation. ... | Content-Class: urn:content-classes:message ... |>present their certificate, enter their password (security ... some users will get a request after ...
      (microsoft.public.inetserver.iis.security)
    • Re: There has to be a better way to develop web applications.
      ... My point is that he was requesting that Microsoft do what ... Not in the terms in which he expressed his "request". ... > Rob has some very valid points here and - especially with MS's customer base ... > - they'd benefit from introducing a more ColdFusion-like RAD web platform. ...
      (microsoft.public.dotnet.framework.aspnet)
    • Re: Theory behind ASP.NET mobile device capabilities?
      ... > collection of HTTP modules ... > HTTP modules are classes that have access to the incoming request. ... > information about the mobile device capabilities is written in the request. ...
      (microsoft.public.dotnet.framework.aspnet.mobile)