[Standards-JIG] pubsub: SubIDs

Bob Wyman bob at wyman.us
Wed Feb 15 01:09:06 UTC 2006


Peter Saint-Andre wrote:
> It seems simplest for the service to always generate subscription
> IDs in order to prevent collisions and such.
	I strongly support this suggestion. Clients are free to map SubIDs
to any other identifiers they may be maintaining or presenting, however, the
SubIDs exchanged with the server should be considered opaque syntax-free
strings and should be assigned by the server.

		bob wyman


-----Original Message-----
From: standards-jig-bounces at jabber.org
[mailto:standards-jig-bounces at jabber.org] On Behalf Of Peter Saint-Andre
Sent: Tuesday, February 14, 2006 4:27 PM
To: standards-jig at jabber.org
Subject: [Standards-JIG] pubsub: SubIDs

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

It seems simplest for the service to always generate subscription IDs in
order to prevent collisions and such. So the client would never include
a 'subid' attribute on its subscription requests (and even if it did the
service might overrride that). The only reason I can see for clients to
generate SubIDs is if the user wants to make the SubID have semantic
meaning (such as the tagging stuff people do for Flickr and weblog posts
and the like). But I still think it's easier for the service to generate
all the SubIDs since IMHO they are to be used for tracking purposes, not
semantic meaning.

Objections?

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

iD8DBQFD8ksTNF1RSzyt3NURAr8eAJ9TqEmNxFh2uBfVmpp9J2YFA5CNeACaAof1
3vIpzIf15Ix5YhLr5d2/HGM=
=qb2X
-----END PGP SIGNATURE-----





More information about the Standards mailing list