Navigation überspringen ([Alt] + [0])

Sitemap | english Version

>> Ressourcen > Archiv > Maurer H. (Ed.)[..] > 20 Hyper-G and [..]

• Über uns
  • Mitarbeiter
  • Aktuelles
  • ... mehr über uns
  • Kontaktinformationen
• Lehre
  • Lehrveranstaltungen
  • LV-Unterlagen
  • Offene Projekte
  • Offene Diplomarbeiten
  • Abschlussarbeiten
• Forschung
  • Forschungsbereiche
  • Projekte
  • Publikationen
  • Partner

• TU Graz
• TUGRAZonline
• Impressum

26/46

20 Hyper-G and WWW

 

Christian Derler, Gerald Mesaric

Imagine although nobody has really been able to do so until now  that you have developed the ultimate information system. Even if you had, you would still have to remain backward compatible with other systems, or users would not be able to upgrade to your system without a lot of trouble. Among others, it was for this reason that Hyper-G was designed to be fully compatible with earlier common information systems like Gopher and WWW. However, Hyper-G is not a new exotic system, but just an extension of WWW, easing some problems that have emerged when using WWW for large amounts of data. Thus Hyper-G should be seen as a powerful WWW server, both for the user and the administrator.

Backward compatibility means, in practice, four things:

1. implementing client gateways, so that you can go on using your favorite browsers to access Hyper-G servers;
2. developing server gateways, so that you can browse WWW and Gopher servers by using Hyper-G viewers and so that you can create hyperlinks to this kind of first-generation information systems;
3. providing tools, so that users and administrators can move their data from WWW and Gopher servers over to the Hyper-G database without much manual intervention;
4. ensuring that WWW editing tools can be used to create Hyper-G pages.

In this chapter we will focus on the interoperability of Hyper-G and WWW, describing the WWW gateway to the clients (wwwmaster) as well as the server gateway provided by the Document Cache Server (dcserver). We will also present a tool to insert any net of HTML documents into a Hyper-G database and describe how HTML documents are stored within the server. If you are interested in the same questions concerning the Gopher information system, read Chapter 21, where Mark McCahill the ``father of Gopher'' explains the cooperation now going on between Gopher and Hyper-G.

 20.1 Accessing Hyper-G servers with WWW clients

 20.2 The server gateway

 20.3 Migration to Hyper-G

 20.4 Hyper-G as a powerful WWW server

 20.5 Further reading