[Standards-JIG] JEP-0060: publish item without an item id

Peter Saint-Andre stpeter at jabber.org
Mon Jun 19 19:52:19 UTC 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

bernhard wrote:
> Example 15 describes how to publish an item without an item id.

In general, refer to http://www.jabber.org/jeps/tmp/jep-0060-1.8.html
rather than http://www.jabber.org/jeps/jep-0060.html (the first link is
much more up to date and will soon replace the official URL).

> Will this item have an automatic generated id?

That's not necessary for the pure event notification scenario. Consider
this:

<message from='pubsub.shakespeare.lit' to='francisco at denmark.lit'>
  <event xmlns='http://jabber.org/protocol/pubsub#event'>
    <items node='elsinore/doorbell'/>
  </event>
</message>

You don't need to delete it, you don't need to retrieve it, all you need
to know is that the doorbell rang.

In the pure event notification scenario, there is no history, just a
stream of events. It's a Heraclitean universe, if you will. ;-)

> Or is the id value "current"?

Definitely not.

> If the item has no id it is not possible to delete it.

True. You can't retrieve it, either.

> I think there should be an automatic generated id.
> If the id is generated the client should be informed about the id value.

The publishing client will be so informed if it is subscribed to the
node it's publishing to (which in general is a good idea).

Peter

- --
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.shtml

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFElwBzNF1RSzyt3NURAsAnAJ4/mj+132FWr4k11fCELSrL8DOylQCgzjS4
cwakgm6BuqNvz23X/HdKdlc=
=4N3x
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060619/93ae81ac/attachment.bin>


More information about the Standards mailing list