8.0

Table Of Contents

Getting started: HTTP

QuarkXPress Server accepts HTTP requests from a browser. You can submit HTTP requests manually

in the form of a URL from a browser or dynamically from a client-server solution.

Regardless of the method you use, the server processes requests and returns rendered layouts in the

HTTP response. Depending on the original request, QuarkXPress Server preferences, and the type of

data being returned (whether that be PDF, JPEG, QXP, XML, or one of the other formats

QuarkXPress Server supports), rendered layouts display in the browser or are saved to a server

location.

Responses returned to a client-server solution can be manipulated based on the functionality built into the

client application. Such a solution may consist of QuarkXPress Server (running on a server computer

connected to a network) plus a front-end application (usually Web-based) that provides a graphical user

interface (GUI) for end users. The front-end application translates the end users' input into HTTP

requests and sends the requests to QuarkXPress Server or QuarkXPress Server Manager. The server

processes the requests and returns rendered layouts.

All you need to use QuarkXPress Server is the ability to generate HTTP GET/POST requests. That

means you can write front-end applications in just about any language that allows you to make HTTP

GET/POST requests.

This Web Integration Guide (WIG) explains the functions available in QuarkXPress Server and how

HTTP requests need to be structured.