Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of willem.jiang@gmail.com
 designates 209.85.160.50 as permitted sender)
Date: Sat, 5 Jan 2013 14:56:48 +0800
From: Willem jiang <willem.jiang@gmail.com>
To: users@camel.apache.org
Message-ID: <1EC1D33EDC19475299B226BAD866C2DB@gmail.com>
In-Reply-To: <1357354473748-5724934.post@n5.nabble.com>
References: <1357354473748-5724934.post@n5.nabble.com>
Subject: Re: Camel websocket disconnect trigger
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

Current Camel websocket manage the web socket connection itself with the =
MemoryWebsocketStore. I'm not sure what kind of resource you need to mana=
ge yourself.

You should be able to know if the client web socket disconnect if you can=
 pass the customer NodeSynchronization into the WebSocketEndpoint. As cur=
rent Camel WebSocket doesn't expose the API, you need to hack the code to=
 pass the reference.


-- =20
Willem Jiang

Red Hat, Inc.
=46useSource is now part of Red Hat
Web: http://www.fusesource.com =7C http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) =
(English)
          http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang =20
Weibo: =E5=A7=9C=E5=AE=81willem


On Saturday, January 5, 2013 at 10:54 AM, aoisagi wrote:

> Hi, I just started playing around with camel-websocket, however, there
> doesn't seem to be a trigger when the client quit the browser. Is there=
 some
> kind of mechanism to detect disconnected socket so I can recycle some
> resources that's dedicated to that socket previously=3F Thanks.
> =20
> =20
> =20
> --
> View this message in context: http://camel.465427.n5.nabble.com/Camel-w=
ebsocket-disconnect-trigger-tp5724934.html
> Sent from the Camel - Users mailing list archive at Nabble.com (http://=
Nabble.com).