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.
After StoryServer version 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 just tcl.
Note that V7 is not StoryServer—it provides much of the same functionality, but has been totally rewritten in Java and is very different. There is no migration path from StoryServer to V7.
StoryServer-based websites often use a distinctive page address style in which the filename consists of several numbers separated by commas. An example URL of this form would be 'http://example.com/foo/0,1245,,00.html'.
- Malik, Om (October 14, 1998). "Vignette is the story". Forbes. Retrieved December 3, 2011.
|This content management system article is a stub. You can help Wikipedia by expanding it.|
|This Web software–related article is a stub. You can help Wikipedia by expanding it.|