If this is your first visit, please click the Sign Up now button to begin the process of creating your account so you can begin posting on our forums! The Sign Up process will only take up about a minute of two of your time.

Results 1 to 2 of 2
  1. #1
    Junior Member
    Join Date
    Nov 2006
    Member #
    I started a job yesterday so I will be unable to answer many of the questions you guys will ask (I have them too). Essentially I will be redeveloping a perl website into a servlet driven website and I was wondering what some of the advantages/disadvantages of going with an xml/xsl display model over straight HTML/CSS. This is a very unique position where I assume I will be given quite a bit of lattitude in developing the basic arcitecture of the website.
    I'm sure you're going to ask, what does this website do? It is best to think of it as a process management system, where there are processes where you add a file and then are allowed to create multiple paths based on what happens with the file as it is processed. Essentially I will be creating dynamic forms that cater to over 700 different processes with different parameters.
    Given this knowledge would you choose to develop a website with a more standard HTML/CSS model or the XML/XSL model, and most importantly, what are the perceived advantages/disadvantages of both?


  3. #2
    Senior Member
    Join Date
    Jun 2005
    Atlanta, GA
    Member #
    1 times
    The key question here is, I would think, whether there are cases where you will have a single XML data source that needs to be converted into several different views in a structured way. That's where using XML+XSL would work. If you always offer the same view into discrete data sources, then you only really need to use HTML+CSS.

Remove Ads

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
All times are GMT -6. The time now is 03:23 PM.
Powered by vBulletin® Version 4.2.3
Copyright © 2020 vBulletin Solutions, Inc. All rights reserved.
vBulletin Skin By: