diff options
| author | Mike Hearn <mike@navi.cx> | 2004-07-06 20:48:50 +0000 |
|---|---|---|
| committer | Mike Hearn <mike@navi.cx> | 2004-07-06 20:48:50 +0000 |
| commit | 0ab190f75e82f40a62dd81c6033941cba99bab39 (patch) | |
| tree | b3578435bce3d246677c3674b5eff5308f9c9a54 /SPECIFICATION | |
| parent | 075e6dda7f81cadc8f52caabd7b73e5323f3288f (diff) | |
| download | libnotify-0ab190f75e82f40a62dd81c6033941cba99bab39.tar.gz | |
We decided NIDs are unique within a session
Diffstat (limited to 'SPECIFICATION')
| -rw-r--r-- | SPECIFICATION | 16 |
1 files changed, 9 insertions, 7 deletions
diff --git a/SPECIFICATION b/SPECIFICATION index ad06638..df9a0a6 100644 --- a/SPECIFICATION +++ b/SPECIFICATION @@ -90,13 +90,15 @@ A notification has the following components: not required (this is for compatibility with KNotify). -Each notification displayed is allocated a unique ID by the server -(FIXME: should this be unique within a session, or just unique while -the notification is active?). This can be used to hide the -notification before the expiration time is reached. It can also be used to -atomically replace the notification with another: this allows you to -(for instance) modify the contents of a notification while it's -on-screen. +Each notification displayed is allocated a unique ID by the server. +This is unique within the session - while the notification server is +running the ID will not be recycled unless the capacity of a uint32 is +exceeded. + +This can be used to hide the notification before the expiration time +is reached. It can also be used to atomically replace the notification +with another: this allows you to (for instance) modify the contents of +a notification while it's on-screen. BACKWARDS COMPATIBILITY |