Lesson plan

StoryServer

StoryServer was the name the company Vignette gave to CNET's web publishing application "PRISM" when they bought it. It used a document publishing model to move templates through various workflow stages, and was thus quite useful to the newly formed Web publishing world. The templates were defined in the Tcl language, using extensions that made StoryServer's internal state and database available. The defining attribute of StoryServer was the caching system which allowed access to pre-generated pages to completely bypass the content generation system, and thus produce these pages as fast as the underlying hardware and Web server software could send them to the network. This gained StoryServer a degree of scalability that most products were incapable of matching. It integrated with HTTP web server platforms and used lazy caching gracefully connected to their 404 "File Not Found" handlers. StoryServer version 4 was released in July 1998 and introduced XML support. After StoryServer 4, Vignette changed the name of the product to "V5", and has named each subsequent version in the same manner. V5 and V6 added support for templates that used Java and ASP rather than tcl. StoryServer-based websites often use a distinctive page address style in which the filename consists of several numbers separated by commas.…

Back to article

Article summary

StoryServer was the name the company Vignette gave to CNET's web publishing application "PRISM" when they bought it. It used a document publishing model to move templates through various workflow stages, and was thus quite useful to the newly formed Web publishing world. The templates were defined in the Tcl language, using extensions that made StoryServer's internal state and database available. The defining attribute of StoryServer was the caching system which allowed access to pre-generated pages to completely bypass the content generation system, and thus produce these pages as fast as the underlying hardware and Web server software could send them to the network. This gained StoryServer a degree of scalability that most products were incapable of matching. It integrated with HTTP web server platforms and used lazy caching gracefully connected to their 404 "File Not Found" handlers. StoryServer version 4 was released in July 1998 and introduced XML support. After StoryServer 4, Vignette changed the name of the product to "V5", and has named each subsequent version in the same manner. V5 and V6 added support for templates that used Java and ASP rather than tcl. StoryServer-based websites often use a distinctive page address style in which the filename consists of several numbers separated by commas.…

Key claims

  1. release date: 1998 — source: Wikipedia · confidence 0.95

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. The record states that the release date is "1998". What evidence would count against this claim?
  3. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  4. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

  1. Wikipedia https://en.wikipedia.org/w/index.php?oldid=1333190493

Key claims and bibliography are generated from the same tracked claims and sources as the article page.