[jdev] Component disocnnection
julien.genestoux at gmail.com
Sat Jan 22 09:58:00 CST 2011
Nope, sending </stream> won't cut it, because Ineed to component to clear
out whatever messages are being processed.
Basically, our components get hundreds of messages per second, some of them
take up to a few seconds to be processed and some of them incur responses to
be sent. What I want for the component is the ability to tell the server :
please don't route any more messages to me, let me send a few more though.
On Sat, Jan 22, 2011 at 6:18 AM, Waqas Hussain <waqas20 at gmail.com> wrote:
> On Sat, Jan 22, 2011 at 12:53 PM, Julien Genestoux
> <julien.genestoux at gmail.com> wrote:
> > Hello,
> > XMPP Components (XEP 0114) are great... but there we have an issue with
> > disconnects. Is there a way to indicate to the servers that this
> > (or instance of this component) will soon be disocnnected and that the
> > server should not send more stanzas toward it?
> > Maybe this is left to the server's implementation?
> > Thanks,
> 1. Send a stream close from the component to the server: </stream:stream>
> 2. Wait for the server to send its own </stream:stream> and close the
> The component may receive stanzas between steps 1 and 2, due to the
> nature of asynchronous communication.
> On Sat, Jan 22, 2011 at 2:39 PM, Tuomas Koski <koski.tuomas at gmail.com>
> > Good point. It would be an excellent feature to have the server to
> > buffer the messages for some time. It would speed up deployments even
> > on busy hours since it would not matter if a component is "off line"
> > for some seconds.
> > Cheers,
> > --
> > Tuomas
> XEP-0225 + XEP-0198
> Waqas Hussain
> JDev mailing list
> Info: http://mail.jabber.org/mailman/listinfo/jdev
> Unsubscribe: JDev-unsubscribe at jabber.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the JDev