8.0
Table Of Contents
- Overview
- New and enhanced features
- Getting started
- Functions
- Function overview
- Render types
- Content modifiers
- Render modifiers
- XML modify
- XML deconstruct and construct
- About XML deconstruct/construct
- xml
- construct
- Deconstructing a project
- Constructing a project
- Working with pages and spreads
- Working with layers
- Working with boxes
- Working with pictures
- Working with text
- Working with tables
- Working with Composition Zones
- Using server XSLT
- Working with lists
- Working with anchored boxes
- Working with placeholders
- Working with metadata
- Working with hidden text
- Administrative Request handlers
- The Modifier DTD
- Sample applications
- Contact Quark
- Legal notice
About administrative request handlers
A request handler is the most powerful way to change the behavior of QuarkXPress Server. With this
method, the QuarkXPress Server XTensions software can completely handle a subset of requests
received by the server. A subset of requests is identified by a namespace string. Every request handler
has a namespace string associated with it.
Namespace
getdocinfo, getdocpoollist, getprojinfo, fileinfo,
addfile, delete, literal, flush, flushall, shutdown,
getprefs, setprefs, and getserverinfo
Response
A QuarkXPress Server response, depending on the
specific request handler.
Logs
If the document is successfully rendered, a
transaction success message is written to the
QuarkXPress Server Transaction Log file. The
transaction entry consists of the date and time of the
request, request type, type of response produced
by the server, size of the response returned in
bytes, and client IP address.
The following is a sample of a transaction entry:
8/4/2004 10:10:43 - getprefs - Type: text/xml -
Size: 2636 - Client: 127.0.0.1
Example GET URL
http://localhost:8080/getserverinfo
Notes
You can add a new request handler. During the
DDSSETUPCBCODE callback, the QuarkXPress
Server XTensions software registers itself as a
request handler via AddCustomRequestHandler,
the QuarkXPress Server XTensions API. The first
parameter of this API is a pointer to a request
handler function implemented in the QuarkXPress
Server XTensions software. The second parameter
is a namespace string that identifies the request.
Whenever a user submits a request that has the
same namespace string as a suffix to the request
URL, the request handler function is called by
QuarkXPress Server with all the user-specified
parameters filled in the ServerRequest structure.
The request handler function then processes the
request and submits the reply in the ServerReply
structure, which QuarkXPress Server
communicates back to the user-agent.
Page 183