DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 2 of 2

Thread: XSLT : server side paging / hundreds of users issues

  1. #1
    tyris Guest

    XSLT : server side paging / hundreds of users issues


    Now that I know the exact term ( i read http://www.dpawson.co.uk/xsl/sect2/paging.html),
    I made some search about paging. They all talk about paging with XSLT on
    the client side. What about the server side? I guess that will be a lot of
    charge for the server if it deals with the transformation, but my xml files
    shouldn’t be too big.

    He do have hundreds of users that will use my web app, so we can't ask them
    to install MSXSL3 for each machine, unregister the old DLL, register the
    new one (as described in http://www.netcrucible.com/xslt/msxml-faq.htm#Q3)...


    What do you think about this? Can it also be well done on server side?

    By the way, I’ve read a doc about a code-signed package that allows you to
    install MSXML3 to people's machines through their web browser but the users
    will still have to remove the side-by-side mode (which means that installing
    the MSXML 3.0 parser will not cause any previously installed version of the
    parser to be replaced). Does someone know something about automating this
    step and avoid users to manually replace the older parser with the newer
    one. (With xmlinst.exe installer tool I guess or is there other better tools?)


    Regards,
    Elise, XML learning girl :-)


  2. #2
    Russell Jones Guest

    Re: XSLT : server side paging / hundreds of users issues

    You can page with XSLT on the server. It can be a heavy load, but --
    depending on your application -- you may be able to minimize the processing
    time required by caching the output and serving that for duplicate requests.
    Caching works best when the data doesn't change often, and when there are
    numerous duplicate requests.

    If your client-side code creates objects using explicit ProgIDs, users don't
    have to have the parser installed in replace mode. For example, use
    CreateObject("MSXML2.DOMDocument.3.0") rather than using the generic ProgID
    CreateObject("MSXML.DOMDocument").

    "tyris" <kea@mailcity.com> wrote in message news:3b56a2c7$1@news.devx.com...
    >
    > Now that I know the exact term ( i read

    http://www.dpawson.co.uk/xsl/sect2/paging.html),
    > I made some search about paging. They all talk about paging with XSLT on
    > the client side. What about the server side? I guess that will be a lot of
    > charge for the server if it deals with the transformation, but my xml

    files
    > shouldn't be too big.
    >
    > He do have hundreds of users that will use my web app, so we can't ask

    them
    > to install MSXSL3 for each machine, unregister the old DLL, register the
    > new one (as described in

    http://www.netcrucible.com/xslt/msxml-faq.htm#Q3)...
    >
    >
    > What do you think about this? Can it also be well done on server side?
    >
    > By the way, I've read a doc about a code-signed package that allows you to
    > install MSXML3 to people's machines through their web browser but the

    users
    > will still have to remove the side-by-side mode (which means that

    installing
    > the MSXML 3.0 parser will not cause any previously installed version of

    the
    > parser to be replaced). Does someone know something about automating this
    > step and avoid users to manually replace the older parser with the newer
    > one. (With xmlinst.exe installer tool I guess or is there other better

    tools?)
    >
    >
    > Regards,
    > Elise, XML learning girl :-)
    >




Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center