In some cases, it is useful for the order of items in a page to be reversed when paging backwards through a result set. These cases are typically when the result page is returned as a series of response stanzas by the wrapper protocol instead of as a single result stanza.
Requesting reverse order for a result set page is done by including a <reversed />
element in the page request.
| # -*- encoding: utf-8 -*- | |
| """ | |
| sleekxmpp.xml.parser | |
| ~~~~~~~~~~~~~~~~~~~~ | |
| This module provides a customized XML parser that restricts | |
| the use of certain XML features as mandated by RFC 6120. | |
| Part of SleekXMPP: The Sleek XMPP Library |
| # -*- coding: utf-8 -*- | |
| """ | |
| xmpp_wsgi_runner for xmppflask (or just XMPPWSGI) | |
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
| This application is intended to be something like a web server bug for | |
| XMPPWSGI and serve XMPPWSGI applications. It is kept simple, but | |
| potentially can be rewritten to handle more load. Future plans are also | |
| support of gevent-like coroutines, but we will need to try to import | |
| gevent's monkey.patch_sockets() to PyPy somehow. |
| #!/usr/bin/env python | |
| # -*- coding: utf-8 -*- | |
| """ | |
| xmpp_wsgi_runner for xmppflask (or just XMPPWSGI) | |
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
| This application is intended to be something like a web server bug for | |
| XMPPWSGI and serve XMPPWSGI applications. It is kept simple, but | |
| potentially can be rewritten to handle more load. Future plans are also | |
| support of gevent-like coroutines, but we will need to try to import |
| # Where self is a ClientXMPP object | |
| self.delRosterItem('[email protected]') | |
| # -or- | |
| self.updateRoster('[email protected]', subscription='remove') |
| # Where self is a ClientXMPP object | |
| self.rosterUpdate('[email protected]', name='Romeo', groups=['Montagues']) |
| # Where self is a SleekXMPP object, and self.backend is some arbitrary | |
| # object that you create depending on the needs of your application. | |
| # self.add_event_handler('presence_subscribe', self.subscribe) | |
| # self.add_event_handler('presence_subscribed', self.subscribed) | |
| # The unsubscribe and unsubscribed handlers will be similar. | |
| # If a component is being used, be sure to set the pfrom parameter | |
| # when sending presences if you are using multiple JIDs for the component, | |
| # such as [email protected] and [email protected]. |
| # Where xmpp is a SleekXMPP object | |
| xmpp.sendPresence(pto='[email protected]', ptype='subscribe') | |
| # -or- | |
| xmpp.sendPresenceSubscription(pto='[email protected]', ptype='subscribe', pnick='Sleek') |
| # Where xmpp is a SleekXMPP object | |
| xmpp.sendPresence(pto='[email protected]', ptype='probe') |
| # Where self is a SleekXMPP object: | |
| # self.add_event_handler('presence_probe', handle_probe) | |
| def handle_probe(self, presence): | |
| sender = presence['from'] | |
| # Populate the presence reply with the agent's current status. | |
| self.sendPresence(pto=sender, pstatus="Busy studying XMPP", pshow="dnd") |