StoryServer

Last updated
StoryServer
Original author(s) CNET (originally PRISM)
Developer(s) Vignette
Stable release
V5, V6
Operating system cross-platform
Available in Tcl, Java, ASP
Type Web publishing

StoryServer was the name the company Vignette gave to CNET's web publishing application "PRISM" when they bought it. [1] 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" [2] handlers. [3]

StoryServer version 4 was released in July 1998 and introduced XML support. [4] 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. An example URL of this form would be 'http://example.com/foo/0,1245,,00.html'.

See also

Related Research Articles

<span class="mw-page-title-main">Apache HTTP Server</span> Open-source web server software

The Apache HTTP Server is a free and open-source cross-platform web server software, released under the terms of Apache License 2.0. It is developed and maintained by a community of developers under the auspices of the Apache Software Foundation.

<span class="mw-page-title-main">HTTP</span> Application protocol for distributed, collaborative, hypermedia information systems

HTTP is an application layer protocol in the Internet protocol suite model for distributed, collaborative, hypermedia information systems. HTTP is the foundation of data communication for the World Wide Web, where hypertext documents include hyperlinks to other resources that the user can easily access, for example by a mouse click or by tapping the screen in a web browser.

<span class="mw-page-title-main">Web server</span> Computer software that distributes web pages

A web server is computer software and underlying hardware that accepts requests via HTTP or its secure variant HTTPS. A user agent, commonly a web browser or web crawler, initiates communication by making a request for a web page or other resource using HTTP, and the server responds with the content of that resource or an error message. A web server can also accept and store resources sent from the user agent if configured to do so.

<span class="mw-page-title-main">Jakarta Servlet</span> Jakarta EE programming language class

A Jakarta Servlet, formerly Java Servlet is a Java software component that extends the capabilities of a server. Although servlets can respond to many types of requests, they most commonly implement web containers for hosting web applications on web servers and thus qualify as a server-side servlet web API. Such web servlets are the Java counterpart to other dynamic web content technologies such as PHP and ASP.NET.

<span class="mw-page-title-main">Proxy server</span> Computer server that makes and receives requests on behalf of a user

In computer networking, a proxy server is a server application that acts as an intermediary between a client requesting a resource and the server providing that resource. It improves privacy, security, and performance in the process.

SOCKS is an Internet protocol that exchanges network packets between a client and server through a proxy server. SOCKS5 optionally provides authentication so only authorized users may access a server. Practically, a SOCKS server proxies TCP connections to an arbitrary IP address, and provides a means for UDP packets to be forwarded. A SOCKS server accepts incoming client connection on TCP port 1080, as defined in RFC 1928.

Information and Content Exchange (ICE) is an XML-based protocol used for content syndication via the Internet. By using XML both sender and receiver have an agreed-upon language in which to communicate. Using a client–server architecture, ICE defines a syndicate/subscribe model that is comparable to the binary publish/subscribe protocol standards used in CORBA and DCOM. However, in ICE messages are delivered through XML, typically over an HTTP connection, rather than through a lower-level binary protocol.

An .htaccess file is a directory-level configuration file supported by several web servers, used for configuration of website-access issues, such as URL redirection, URL shortening, access control, and more. The 'dot' before the file name makes it a hidden file in Unix-based environments.

The ArsDigita Community System (ACS) was an open source toolkit for developing community web applications developed primarily by developers associated with ArsDigita Corporation. It was licensed under the terms of the GNU GPL, and is one of the most famous products to be based completely on AOLserver. Although there were several forks of the project, the only one that is still actively maintained is OpenACS.

A permalink or permanent link is a URL that is intended to remain unchanged for many years into the future, yielding a hyperlink that is less susceptible to link rot. Permalinks are often rendered simply, that is, as clean URLs, to be easier to type and remember. Most modern blogging and content-syndication software systems support such links. Sometimes URL shortening is used to create them.

In computer hypertext, a URI fragment is a string of characters that refers to a resource that is subordinate to another, primary resource. The primary resource is identified by a Uniform Resource Identifier (URI), and the fragment identifier points to the subordinate resource.

A web content management system is a software content management system (CMS) specifically for web content. It provides website authoring, collaboration, and administration tools that help users with little knowledge of web programming languages or markup languages create and manage website content. A WCMS provides the foundation for collaboration, providing users the ability to manage documents and output for multiple author editing and participation. Most systems use a content repository or a database to store page content, metadata, and other information assets the system needs.

A web framework (WF) or web application framework (WAF) is a software framework that is designed to support the development of web applications including web services, web resources, and web APIs. Web frameworks provide a standard way to build and deploy web applications on the World Wide Web. Web frameworks aim to automate the overhead associated with common activities performed in web development. For example, many web frameworks provide libraries for database access, templating frameworks, and session management, and they often promote code reuse. Although they often target development of dynamic web sites, they are also applicable to static websites.

Edge Side Includes (ESI) is a small markup language for edge level dynamic web content assembly. The purpose of ESI is to tackle the problem of web infrastructure scaling. It is an application of edge computing.

A proxy auto-config (PAC) file defines how web browsers and other user agents can automatically choose the appropriate proxy server for fetching a given URL.

<span class="mw-page-title-main">Web template system</span> System in web publishing

A web template system in web publishing allows web designers and developers to work with web templates to automatically generate custom web pages, such as the results from a search. This reuses static web page elements while defining dynamic elements based on web request parameters. Web templates support static content, providing basic structure and appearance. Developers can implement templates from content management systems, web application frameworks, and HTML editors.

<span class="mw-page-title-main">HTTP ETag</span> Communications protocol

The ETag or entity tag is part of HTTP, the protocol for the World Wide Web. It is one of several mechanisms that HTTP provides for Web cache validation, which allows a client to make conditional requests. This mechanism allows caches to be more efficient and saves bandwidth, as a Web server does not need to send a full response if the content has not changed. ETags can also be used for optimistic concurrency control to help prevent simultaneous updates of a resource from overwriting each other.

<span class="mw-page-title-main">Silverstripe CMS</span> Content management system

Silverstripe CMS is a free and open source content management system (CMS) and framework for creating and maintaining websites and web applications. It provides an out of the box web-based administration panel that enables users to make modifications to parts of the website, which includes a WYSIWYG website editor. The core of the software is Silverstripe Framework, a PHP Web application framework.

<span class="mw-page-title-main">TYPO3</span>

TYPO3 is a Web Content management system (CMS) written in the programming language PHP. It is able to run on a variety of web servers, such as Apache, Nginx, or Internet Information Services (IIS), and on many operating systems, including Linux, Microsoft Windows, FreeBSD, macOS, and OS/2. It is free and open-source software released under the GNU General Public License version 2.

ASP.NET Web Forms is a web application framework and one of several programming models supported by the Microsoft ASP.NET technology. Web Forms applications can be written in any programming language which supports the Common Language Runtime, such as C# or Visual Basic. The main building blocks of Web Forms pages are server controls, which are reusable components responsible for rendering HTML markup and responding to events. A technique called view state is used to persist the state of server controls between normally stateless HTTP requests.

References

  1. Malik, Om (October 14, 1998). "Vignette is the story". Forbes. Archived from the original on February 5, 2012. Retrieved December 3, 2011.
  2. "RFC 9110". Internet Engineering Task Force (IETF).
  3. "US5740430A Patent". United States Patent and Trademark Office (USPTO).
  4. Dudrow, Andrea (1998-07-09). "Vignette to ship latest StoryServer". MacWeek. Archived from the original on January 11, 2000. Retrieved 2014-09-07.{{cite news}}: CS1 maint: unfit URL (link)