2017

Table Of Contents
USING QUARKXPRESS SERVER
32 | A Guide to QuarkXPress Server 2017
L
ooking up a namespace
T
his guide lists the namespaces for every QuarkXPress Server function. There is no
single list of namespaces because some functions do not require a particular
namespace or are available in multiple namespaces. To determine which namespace
you want to use:
In this Guide, go to the page that documents the render type you want to use.1.
(
For more information, see “
U
nderstanding render types
.
”)
L
ocate the Namespace row. If the render type or function has an associated
2
.
namespace, that namespace is listed here.
Third-party XTensions can add their own namespaces. For information about a
third-party namespace, see the documentation for the XTensions module that adds
that namespace.
Understanding QuarkXPress Server parameters
Parameters let you control the details of how a request is executed. For example,
you can use the
page parameter to create a request that returns only the third page
of a project:
http://QXPServer:8080/jpeg/project1.qxp?page=3
You can include multiple parameters in the same request; simply separate them
with an ampersand (&). For example, here’s a new version of the above URL that
returns page three at a scale of 50%:
http://QXPServer:8080/jpeg/project1.qxp?page=3&scale=.5
Looking up a parameter
This Guide lists the parameters that are available for every QuarkXPress Server
function. To determine which parameters you can use with a request:
In this Guide, go to the page that documents the the render type you want or
1.
the function you want to use. (For more information, see “Understanding render
types“ and “Understanding render modifiers.”)
Locate the Parameters row. This row lists all available parameters, and includes
2.
a description and a list of valid values for each parameter.
Supported interfaces
The following interfaces are available in QuarkXPress Server:
HTTP: Lets you interact with the server using URLs that contain calls or point to
XML files that contain calls. You can write client applications in any language
that supports HTTP requests. For more information, see “
Getting started: HTTP“.
HTTPS: Provides secure HTTP access.
Web services: Lets you interact with the server via Web services using the
QuarkXPress Server Manager object model. You can write client applications in