Bug 622 - RFE: Xprt's default BIGREQUESTS extension buffer size should be 8MB
Summary: RFE: Xprt's default BIGREQUESTS extension buffer size should be 8MB
Status: RESOLVED FIXED
Alias: None
Product: xprint
Classification: Unclassified
Component: Server: Other (show other bugs)
Version: unspecified
Hardware: All All
: high enhancement
Assignee: Roland Mainz
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-15 19:57 UTC by Roland Mainz
Modified: 2004-05-14 14:43 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
Patch for 2004-05-15-trunk (5.53 KB, patch)
2004-05-16 00:41 UTC, Roland Mainz 		no flags Details | Splinter Review
View All

Description Roland Mainz 2004-05-15 19:57:10 UTC 
RFE: Xprt's default BIGREQUESTS extension buffer size should be 8MB

This is basically the same as xprint.mozdev.org bug 3918
(http://xprint.mozdev.org/bugs/show_bug.cgi?id=3918 - "RFE: Increase the maximum
request size for the Xprt server from 1MB to 8MB") - the switch to the Xorg CVS
has undone this fix... ;-(

References:
- Xfree86 bug 460
(http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=460 - "RFE: Buffer
size for the BIGREQUESTS extension should be tuneable") to port the patch over
to Xfree86 and X11R6.6
- xprint.mozdev.org bug 3918 (http://xprint.mozdev.org/bugs/show_bug.cgi?id=3918
- "RFE: Increase the maximum request size for the Xprt server from 1MB to 8MB").
Comment 1 Roland Mainz 2004-05-16 00:41:27 UTC 
Created attachment 289 [details] [review]
Patch for 2004-05-15-trunk
Comment 2 Roland Mainz 2004-05-16 00:43:44 UTC 
Patch checked-in...

Checking in xc/ChangeLog;
/cvs/xorg/xc/ChangeLog,v  <--  ChangeLog
new revision: 1.26; previous revision: 1.25
done
Checking in xc/programs/Xserver/Xprint/Init.c;
/cvs/xorg/xc/programs/Xserver/Xprint/Init.c,v  <--  Init.c
new revision: 1.4; previous revision: 1.3
done

... marking bug as FIXED.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.