* Sergey Dobrov <bin...@jrudevels.org> [2016-10-22 09:33]: > On 21/10/2016 23:47, forenjunkie wrote: > > Especially #publish-options is missing from a lot of servers. > > Missing as in the server is capable of it but does deliberately not > > publish that feature. > > As I understand, this is just an example and they decided to use the > #publish-options just to make the conversation between the server and the > client more concise. There should be no problem to perform the node > configuration in a separate query and still comply with the XEP.
XEP-0223 says: | In order for the client to reliably persist private information, the | virtual pubsub service must also support the "publish-options" feature | defined in XEP-0060. [...] | | Before an account owner attempts to complete any of the use cases | defined herein, its client SHOULD verify that the account owner's | server supports both PEP and the "publish-options" feature. [...] | | The server MUST return an identity of "pubsub/pep" and include the | "publish-options" feauture [...]. Given that XEP-0060 doesn't clearly specify how the server should handle pubsub#persist_items and pubsub#access_model when submitted as publish-options, I think XEP-0223 should not refer to publish-options and rather just mandate an appropriate node configuration. Holger _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
