From 903e0f6f0f0ec54151640fc459ff03dcba0522af Mon Sep 17 00:00:00 2001 From: Alan Coopersmith Date: Sat, 27 Nov 2010 10:46:44 -0800 Subject: [PATCH] Xserver-spec: Delete DBE Idioms section The code has been gone for a while Signed-off-by: Alan Coopersmith Reviewed-by: Jeremy Huddleston Reviewed-by: Keith Packard Signed-off-by: Keith Packard --- doc/xml/Xserver-spec.xml | 64 ---------------------------------------- 1 file changed, 64 deletions(-) diff --git a/doc/xml/Xserver-spec.xml b/doc/xml/Xserver-spec.xml index 62992826f..ae15346f7 100644 --- a/doc/xml/Xserver-spec.xml +++ b/doc/xml/Xserver-spec.xml @@ -1361,70 +1361,6 @@ The sample server implementation for these routines is in Xserver/os/util.c. -
- Idiom Support - -The DBE specification introduces the notion of idioms, which are -groups of X requests which can be executed more efficiently when taken -as a whole compared to being performed individually and sequentially. -This following server internal support to allows DBE -implementations, as well as other parts of the server, -to do idiom processing. - - -
- - xReqPtr PeekNextRequest(xReqPtr req, ClientPtr client, Bool readmore) -
-If req is NULL, the return value will be a pointer to the start of the -complete request that follows the one currently being executed for the -client. If req is not NULL, the function assumes that req is a -pointer to a request in the client's request buffer, and the return -value will be a pointer to the the start of the complete request that -follows req. If the complete request is not available, the function -returns NULL; pointers to partial requests will never be returned. If -(and only if) readmore is TRUE, PeekNextRequest should try to read an -additional request from the client if one is not already available in -the client's request buffer. If PeekNextRequest reads more data into -the request buffer, it should not move or change the existing data. - - -
- - void SkipRequests(xReqPtr req, ClientPtr client, int numskipped) -
-The requests for the client up to and including the one specified by -req will be skipped. numskipped must be the number of requests being -skipped. Normal request processing will resume with the request that -follows req. The caller must not have modified the contents of the -request buffer in any way (e.g., by doing byte swapping in place). - - -Additionally, two macros in os.h operate on the xReq -pointer returned by PeekNextRequest: -
- - int ReqLen(xReqPtr req, ClientPtr client) -
-The value of ReqLen is the request length in bytes of the given xReq. -
- - otherReqTypePtr CastxReq(xReq *req, otherReqTypePtr) -
-The value of CastxReq is the conversion of the given request pointer -to an otherReqTypePtr (which should be a pointer to a protocol -structure type). Only those fields which come after the length field -of otherReqType may be accessed via the returned pointer. - - -Thus the first two fields of a request, reqType and data, can be -accessed directly using the xReq * returned by PeekNextRequest. The -next field, the length, can be accessed with ReqLen. Fields beyond -that can be accessed with CastxReq. This complexity was necessary -because of the reencoding of core protocol that can happen due to the -BigRequests extension. - -