jcarr
/
libnotify
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

rename CapsQuery to GetCapabilities

This commit is contained in:
Mike Hearn 2004-07-01 23:03:12 +00:00
parent 203f183810
commit a0897d8451
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
SPECIFICATION
View File

@ -74,7 +74,7 @@ A notification has the following components:
- An array of actions. The actions send a request message back to the
notification client when invoked. This functionality may not be
implemented by the notification server, conforming clients should
check if it is available before using it (see the CapsQuery message
check if it is available before using it (see the GetCapabilities message
in the PROTOCOL section). An implementation is free to ignore any
requested by the client. As an example one possible rendering of
actions would be as buttons in the notification popup.
@ -107,7 +107,7 @@ assumptions about the presentation and abilities of the notification
server: the message content is the most important thing.
Clients can check with the server what capabilities are supported
using the CapsQuery message. See the PROTOCOL section.
using the GetCapabilities message. See the PROTOCOL section.
If a client requires a response from a passive popup, it should be
coded such that a non-focus-stealing message box can be used instead
@ -165,7 +165,7 @@ PROTOCOL
The following messages must be supported by all implementations.
* CapsQuery
* GetCapabilities
This message takes no parameters.