<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Latest topics for the forum "TODO / New Features"]]></title>
		<link>http://www.kaazing.org/forums/forums/show/9.page</link>
		<description><![CDATA[The newest discussed topics in the forum "TODO / New Features"]]></description>
		<generator>JForum - http://www.jforum.net</generator>
			<item>
				<title>XMPP Notification on Hard Client Disconnect</title>
				<description><![CDATA[ Hello,<br /> <br /> I think it would be an amazing feature to (as a configuration option) have kaazing drop a XMPP presence message onto the wire in the case where the client hard-disconnects, most notably when they browse away from a connected page w/o any kind of problematically-controlled disconnection.<br /> <br /> If my back-end servers listened to XMPP presence messages (they do), then this would be extremely useful for virtual real-time server-side feedback when a user browsed away.  I can use that information in a number of ways, not the least of which is to force a server side session resource clean-up w/o having to wait for tradition session time-outs.  That's always a huge issue in web development: knowing exactly when the user left your site.  This would give you this.<br /> <br /> I've poked around the code and am trying to understand it.  I've been able to tap into communication by instrumenting IoHandlerAdapter.  I can see the various communication channels being created/destroyed/etc, including the closures when the user navs away abruptly.<br /> <br /> Problems to be solved:<br /> <br /> 1) Capture the XMPP session creation based on jid.  This is the easiest bit since I can already see that &lt;iq&gt;&lt;bind&gt; message come across the wire including the &lt;jid&gt; field, so there's probably an easy way to associate this jid with a socket/session someplace in a lookup table.<br /> <br /> 2) Trap the hard closures (even better if we can identify them as hard closures) and associate the closed channel with the jid in our lookup table.  This is probably the hard part.<br /> <br /> 3) Drop a kaazing-generated presence message on the XMPP wire telling everyone the user has disconnected.  If we've got this far this step should be straightforward since kaazing is clearly already connected to XMPP and able to communicate w/it.<br /> <br /> Not sure if continued poking in IoHandlerAdapter is the right direction, perhaps an XmppIoHandlerAdapter extension?  I'm still trying to figure out the difference between CSE and SSE channels.<br /> <br /> Greg]]></description>
				<guid isPermaLink="true">http://www.kaazing.org/forums/posts/preList/87/430.page</guid>
				<link>http://www.kaazing.org/forums/posts/preList/87/430.page</link>
				<pubDate><![CDATA[Fri, 21 Aug 2009 18:56:41]]> GMT</pubDate>
				<author><![CDATA[ gzoller]]></author>
			</item>
	</channel>
</rss>