summaryrefslogtreecommitdiffstats
path: root/clipboard/clipboard-extensions.txt
diff options
context:
space:
mode:
authorHeinrich Wendel <lanius@gentoo.org>2003-07-09 14:21:05 +0000
committerHeinrich Wendel <lanius@gentoo.org>2003-07-09 14:21:05 +0000
commit791f359c0a03dd36e716a9a040a2e4ea620b4059 (patch)
tree0145f4807bfc4afbcdda8308e44a1f982d587697 /clipboard/clipboard-extensions.txt
parentc93d9bc85d7bc76c7ece39f3b7fb33cfab807c2d (diff)
downloadxdg-specs-791f359c0a03dd36e716a9a040a2e4ea620b4059.tar.xz
added extension spec
Diffstat (limited to 'clipboard/clipboard-extensions.txt')
-rw-r--r--clipboard/clipboard-extensions.txt39
1 files changed, 39 insertions, 0 deletions
diff --git a/clipboard/clipboard-extensions.txt b/clipboard/clipboard-extensions.txt
new file mode 100644
index 0000000..ceed6ca
--- /dev/null
+++ b/clipboard/clipboard-extensions.txt
@@ -0,0 +1,39 @@
+
+ Selection target _NET_MAX_SELECTION_SIZE
+
+ When a client encounters target _NET_MAX_SELECTION_SIZE in
+ SelectionRequest event, it should use its value as a limit for the
+ following targets in the same request (i.e. the request should be of type
+ MULTIPLE). The
+ _NET_MAX_SELECTION_SIZE target should be always the first target in the
+ MULTIPLE request.
+
+ The target _NET_MAX_SELECTION_SIZE is a side-effect target, as described
+ in ICCCM section 2.6.3. When handling this target, the matching property on
+ the requestor window should be of type XA_INTEGER, format 32, with 2
+ elements.
+
+ If the selection owner's connection to the X server is local, the first
+ element is used as the limit, otherwise the second element is used as the
+ limit. A local connection is identified by a value of XDisplayString() with
+ the first character ':', for example, ":0.0". A value of -1 for either
+ element means no limit.
+
+ The value should limit the sum of the sizes in the request, not separately
+ each of them. The client should reject subsequent targets if they would
+ cause the total amount of data transferred for all targets to exceed the
+ limit. Note that there is no requirement that if one target is rejected,
+ all other targets will be rejected or all that subsequent targets will be
+ rejected.
+
+ Clients are not required to limit the data size precisely to the given
+ value. If the computation of the data size would be expensive for the
+ client, a certain reasonable inaccurancy is allowed. In other words, if the
+ client for various reasons doesn't know exact size of the data to be
+ transfered, it should try to estimate it, rather than transfering data with
+ size that is possibly magnitudes larger.
+
+ The intent of this target is to avoid unwanted large transfers, so it
+ should be requsted only by xclipboard-like tools. They should use a request
+ of type MULTIPLE with _NET_MAX_SELECTION_SIZE as the first target in the
+ MULTIPLE request, with the requested target(s) after it.