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

On 9/10/09 8:57 AM, Mads Randstoft wrote:
> Hi!
> 
> Since no one have opposed my suggestion to add priority to PubSub items,

I haven't really had a chance to look at it yet. Still catching up on
email threads. :)

> I am proposing the following:
> 
> To the XSD, relpace item with the following:
> <xs:element name='item'>
>     <xs:complexType>
>       <xs:sequence minOccurs='0'>
>         <xs:any namespace='##other'/>
>       </xs:sequence>
>       <xs:attribute name='id' type='xs:string' use='optional'/>
>       <xs:attribute name='priority' type='xs:byte' use='optional'/>
>     </xs:complexType>
>   </xs:element>

Do you propose adding the 'priority' attribute to an existing pubsub
namespace (e.g., http://jabber.org/protocol/pubsub or
http://jabber.org/protocol/pubsub#event) or do you propose that this
attribute will be qualified by a different namespace (say, by
urn:xmpp:pubsub:queueing:0)? In your original email you said it might be
a namespaced attribute, not a core pubsub attribute. I ask, because it's
unclear to me what a regular pubsub implementation would do with this
information.

> And in the documentation add the following about prioritized items:
> 
> The priority is an advisory, used to implementors discression, an
> example could be sending events on a low bandwith link, and let the
> sending component handle priority to the other end.

It's not clear to me what this means. And advisory regarding how
"important" the event is?

> The attribute value is defined like presence priorities, from 0-127
> higher values means higher priorities. No priority, like presence means
> 0 priority (lowest)

The range for xs:byte is -128 to +127, not 0 to 127. Perhaps you want
unsignedByte (0 to 255) or you want to say that negative values are ignored?

Peter

- --
Peter Saint-Andre
https://stpeter.im/


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

iEYEARECAAYFAkqpr+UACgkQNL8k5A2w/vzYIQCcCUYTvbHNhiaruyfO6NeADDza
mzQAoKaxd8AHcTcK+wtXByF5YUlzwa4H
=udQw
-----END PGP SIGNATURE-----

Reply via email to