Jump to content

Zeus Web Server: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Monkbot (talk | contribs)
Bots
3,695,952 edits
m Task 18 (cosmetic): eval 9 templates: del empty params (1×); hyphenate params (13×);
mNo edit summary
Line 5: Line 5:
Zeus was designed to be a high-performance web server<ref>{{cite web|url=http://www.zeus.com/products/zws |title=Web Server Software |publisher=Zeus |access-date=2008-12-21}}</ref> and was commonly used by hardware vendors submitting [[Standard Performance Evaluation Corporation|SPECweb99]] benchmarks for their hardware.<ref>{{cite web |url=http://www.spec.org/web99/results/web99.html |title=All SPECweb99 Results |publisher=SPEC |date=Nov 21, 2005 |access-date=2008-12-21}}</ref> The SPECweb99 benchmark was retired in 2005 and replaced by [[SPECweb2005]].<ref>{{cite web |url=http://spec.org/retired.html |title=Retired SPEC Benchmarks |publisher=SPEC |access-date=2008-12-21}}</ref> While some SPECweb2005 submissions were made using Zeus, by 2008 it was no longer among the top performers.<ref>{{cite web |url=http://spec.org/web2005/results/web2005.html |title=All SPECweb2005 Results |publisher=SPEC |date=Dec 19, 2008 |access-date=2008-12-21}}</ref>
Zeus was designed to be a high-performance web server<ref>{{cite web|url=http://www.zeus.com/products/zws |title=Web Server Software |publisher=Zeus |access-date=2008-12-21}}</ref> and was commonly used by hardware vendors submitting [[Standard Performance Evaluation Corporation|SPECweb99]] benchmarks for their hardware.<ref>{{cite web |url=http://www.spec.org/web99/results/web99.html |title=All SPECweb99 Results |publisher=SPEC |date=Nov 21, 2005 |access-date=2008-12-21}}</ref> The SPECweb99 benchmark was retired in 2005 and replaced by [[SPECweb2005]].<ref>{{cite web |url=http://spec.org/retired.html |title=Retired SPEC Benchmarks |publisher=SPEC |access-date=2008-12-21}}</ref> While some SPECweb2005 submissions were made using Zeus, by 2008 it was no longer among the top performers.<ref>{{cite web |url=http://spec.org/web2005/results/web2005.html |title=All SPECweb2005 Results |publisher=SPEC |date=Dec 19, 2008 |access-date=2008-12-21}}</ref>


In addition to [[static content]] serving, Zeus supportis [[dynamic content]] via [[Common Gateway Interface|CGI]], [[FastCGI]], [[Apache JServ]], [[Internet Server Application Programming Interface|ISAPI]], [[Netscape Server Application Programming Interface|NSAPI]], [[mod_perl]], [[Server Side Includes|SSI]] and Zeus Distributed Authentication and Content (ZDAC), a proprietary FastCGI-like protocol. While Zeus mainly competed with other commercial web servers such as [[Oracle iPlanet Web Server]], it also includes a high degree of compatibility with [[Apache HTTP Server]] (including [[.htaccess]] support and a [[URL rewriting]] system comparable to Apache's <tt>mod_rewrite</tt>), with the expectation that Apache users would migrate to Zeus as their server load increased.<ref>{{cite news |first=John |last=Clyman |url=https://www.pcmag.com/article2/0,2817,11536,00.asp |work=Server's Advantage PC Magazine Editor's Choice Winner |title=Zeus Web Server 4.0 |publisher=PC Magazine |date=2002-01-15 |access-date=2008-12-21}}</ref> NSAPI and ISAPI were added to ease migrations from [[Internet Information Services|Microsoft IIS]] and Sun Java System Web Server.
In addition to [[static content]] serving, Zeus supported [[dynamic content]] via [[Common Gateway Interface|CGI]], [[FastCGI]], [[Apache JServ]], [[Internet Server Application Programming Interface|ISAPI]], [[Netscape Server Application Programming Interface|NSAPI]], [[mod_perl]], [[Server Side Includes|SSI]] and Zeus Distributed Authentication and Content (ZDAC), a proprietary FastCGI-like protocol. While Zeus mainly competed with other commercial web servers such as [[Oracle iPlanet Web Server]], it also included a high degree of compatibility with [[Apache HTTP Server]] (including [[.htaccess]] support and a [[URL rewriting]] system comparable to Apache's <tt>mod_rewrite</tt>), with the expectation that Apache users would migrate to Zeus as their server load increased.<ref>{{cite news |first=John |last=Clyman |url=https://www.pcmag.com/article2/0,2817,11536,00.asp |work=Server's Advantage PC Magazine Editor's Choice Winner |title=Zeus Web Server 4.0 |publisher=PC Magazine |date=2002-01-15 |access-date=2008-12-21}}</ref> NSAPI and ISAPI were added to ease migrations from [[Internet Information Services|Microsoft IIS]] and Sun Java System Web Server.


== See also ==
== See also ==

Revision as of 21:57, 21 January 2021

Zeus Web Server is a discontinued proprietary web server for Unix and Unix-like platforms (including Solaris, FreeBSD, HP-UX and Linux). It was developed by Zeus Technology, a software company located in Cambridge, England. The original authors and company founders are University of Cambridge graduates Damian Reeves and Adam Twiss.

Support for AIX, Tru64, and Mac OS X was dropped on 10 June 2008.[1] No new ZWS releases have been made since January 2010,[2] and the company no longer offers a similar server solution. In July 2011, the company was acquired by Riverbed Technology,[3] who ended support for ZWS on November 30, 2014.[4]

Zeus was designed to be a high-performance web server[5] and was commonly used by hardware vendors submitting SPECweb99 benchmarks for their hardware.[6] The SPECweb99 benchmark was retired in 2005 and replaced by SPECweb2005.[7] While some SPECweb2005 submissions were made using Zeus, by 2008 it was no longer among the top performers.[8]

In addition to static content serving, Zeus supported dynamic content via CGI, FastCGI, Apache JServ, ISAPI, NSAPI, mod_perl, SSI and Zeus Distributed Authentication and Content (ZDAC), a proprietary FastCGI-like protocol. While Zeus mainly competed with other commercial web servers such as Oracle iPlanet Web Server, it also included a high degree of compatibility with Apache HTTP Server (including .htaccess support and a URL rewriting system comparable to Apache's mod_rewrite), with the expectation that Apache users would migrate to Zeus as their server load increased.[9] NSAPI and ISAPI were added to ease migrations from Microsoft IIS and Sun Java System Web Server.

See also

References

  1. ^ "Archived copy". Archived from the original on November 6, 2012. Retrieved December 21, 2008.{{cite web}}: CS1 maint: archived copy as title (link)
  2. ^ "Archived copy". Archived from the original on November 21, 2012. Retrieved May 23, 2012.{{cite web}}: CS1 maint: archived copy as title (link)
  3. ^ "Riverbed Expands IT Performance Business with Acquisition of Zeus Technology". Riverbed Technology. Retrieved 8 September 2013.
  4. ^ "Hardware & Software End of Life Policy". Riverbed Technology. Retrieved 10 February 2014.
  5. ^ "Web Server Software". Zeus. Retrieved 2008-12-21.
  6. ^ "All SPECweb99 Results". SPEC. Nov 21, 2005. Retrieved 2008-12-21.
  7. ^ "Retired SPEC Benchmarks". SPEC. Retrieved 2008-12-21.
  8. ^ "All SPECweb2005 Results". SPEC. Dec 19, 2008. Retrieved 2008-12-21.
  9. ^ Clyman, John (2002-01-15). "Zeus Web Server 4.0". Server's Advantage PC Magazine Editor's Choice Winner. PC Magazine. Retrieved 2008-12-21.
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=Zeus_Web_Server&oldid=1001897218"