[Fwd: [Moderator Action] Server Side Magic.]

From: Philipp Hoschka (ph@w3.org)
Date: Tue, Jun 19 2001

  • Next message: Philipp Hoschka: "[Fwd: [Moderator Action] Server Side Magic.]"

    Message-ID: <3B2EFE18.63BBB33B@w3.org>
    Date: Tue, 19 Jun 2001 09:24:08 +0200
    From: Philipp Hoschka <ph@w3.org>
    To: www-tv@w3.org, jvierine@mail.nisula.cs.hut.fi
    Subject: [Fwd: [Moderator Action] Server Side Magic.]
    
    
    Juha,
    
    I'm forwarding this mail to www-tv.
    
    You need to join the www-tv list to post to it. Otherwise, your mail
    will go to me as moderator, and forwarded, which may incur a delay.
    This is to prevent spam being sent to www-tv.
    
    -Philipp
    
    

    attached mail follows:


    Date: Mon, 18 Jun 2001 12:22:06 -0400 (EDT)
    From: Juha Vierinen <jvierine@mail.niksula.cs.hut.fi>
    To: www-mobile@w3.org, www-tv@w3.org
    Message-ID: <Pine.SGI.4.20.0106181836380.31343-100000@jolly.cs.hut.fi>
    Subject: [Moderator Action] Server Side Magic. 
    
    Hello, 
    
    We are planning to test CC/PP with a web servlet and a browser[1].
    The CC/PP information can already be sent with the HTTP request in our
    browser. We also have implemented a servlet stub that reads the CC/PP
    information and makes it accessible. The problem is with the server logic.
    
    The server has to do some magic, to come up with a page which fits the
    client. One way to do this would be to have some kind of data structure,
    which contains all the different possibilities to render the page,
    all of them attached to a CC/PP file containing a profile. From this it
    would be possible to some kind of best-fit page to send. 
    
    One simple example would be a site consisting of XML files. Every XML page
    has, say three different stylesheets (XSL), which are designed for three
    different sized displays. Each stylesheet contains, in CC/PP,  the size of
    the page. When a request comes, we calculate, which stylesheet tranforms
    the XML file nearest to the clients device. For this scenario, we would
    nead every file to contain a reference to a CC/PP file, or there has to be
    some data structure describing the site. 
    
    Is there any standardized language for describing a such a site? There are
    propably many other ways to do this, which are they. I can imagine that
    there has been a lot of talk related to this, but I haven't found
    anything. Can someone give me a hint on where to look?
    
    
    [1] The XSmiles XML Browser http://www.xsmiles.org
        + Support for SMIL, SVG, XSL-FO.
    
    
    Juha Vierinen - XSmiles.org