[Standards-JIG] JEP-0060: requesting all pending subscription requests

Peter Saint-Andre stpeter at jabber.org
Thu May 4 16:51:04 UTC 2006


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

A while back, Ralph pointed out that the use of Ad-Hoc Commands to
request all pending subscription requests seems a bit out of place in
Section 8.6.1 of JEP-0060 1.8pre*:

http://www.jabber.org/jeps/tmp/jep-0060-1.8.html#owner-subreq-all

The current flow is as follows:

******

1. Owner requests pending subscription requests

<iq type='set'
    from='hamlet at denmark.lit/elsinore'
    to='pubsub.shakespeare.lit'
    id='pending1'>
  <command xmlns='http://jabber.org/protocol/commands'
           node='http://jabber.org/protocol/pubsub#get-pending'
           action='execute'/>
</iq>

2. Service responds with data form to be populated

<iq type='result'
    from='pubsub.shakespeare.lit'
    to='hamlet at denmark.lit/elsinore'
    id='pending1'>
  <command xmlns='http://jabber.org/protocol/commands'
           sessionid='pubsub-get-pending:20031021T150901Z-600'
           node='http://jabber.org/protocol/pubsub#get-pending'
           status='executing'
           action='execute'>
    <x xmlns='jabber:x:data' type='form'>
      <field type='list-single' var='pubsub#node'>
        <option><value>blogs/princely_musings</value></option>
        <option><value>news/news_from_elsinore</value></option>
      </field>
    </x>
  </command>
</iq>

3. Owner requests all pending subscription requests for a node

<iq type='set' to='pubsub.shakespeare.lit' id='pending2'>
  <command xmlns='http://jabber.org/protocol/commands'
           sessionid='pubsub-get-pending:20031021T150901Z-600'
           node='http://jabber.org/protocol/pubsub#get-pending'
           action='execute'>
    <x xmlns='jabber:x:data' type='submit'>
      <field var='pubsub#node'>
        <value>blogs/princely_musings</value>
      </field>
    </x>
  </command>
</iq>

4. Service responds with success

<iq type='result'
    from='pubsub.shakespeare.lit'
    to='hamlet at denmark.lit/elsinore'
    id='pending2'/>

5. Service sends messages containing subscription requests to owner

******

It seems a lot simpler to use something like the following alternative
flow with defined XML:

******

1. Owner requests all pending subscription requests for a node

<iq type='get'
    from='hamlet at denmark.lit/elsinore'
    to='pubsub.shakespeare.lit'
    id='get-pending-1'>
  <get-pending xmlns='http://jabber.org/protocol/pubsub#owner'
               node='blogs/princely_musings'/>
</iq>

2. Service responds with success

<iq type='result'
    from='pubsub.shakespeare.lit'
    to='hamlet at denmark.lit/elsinore'
    id='get-pending-1'/>

3. Service sends messages containing subscription requests to owner

******

Are there any objections to simplifying this use case? I don't see a
strong reason to have a dependency on JEP-0050 here, and now is our
chance to clean this up (I foresee few modifications to JEP-0060 after
we publish 1.8).

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

iD8DBQFEWjD4NF1RSzyt3NURAjPhAJ9Hn/pTQr/4cxuk83wZ597ceh7YAwCg0D2N
PA7tK1kaL7O4RrEmzmeCX+A=
=hrkh
-----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/20060504/ccff6c8b/attachment.bin>


More information about the Standards mailing list