dev@grizzly.java.net

Re: [Grizzly2.0 - Issue 3] Attaching a Connection object to the SelectionKey

From: ash2k! <ash2kk_at_gmail.com>
Date: Wed, 18 Jun 2008 12:42:55 -0700 (PDT)

Hi!

Jeanfrancois Arcand-2 wrote:
>
> What peoples thinks?
>
I asked some time ago about this thing
http://www.nabble.com/Question-about-http-on-grizzly-tt16846432.html - i
implemented this server (without grizzly, just plain NIO) and i use a simple
hashtable for storing connection related info in it. selectionkey is used as
a key and special class with connection info as a value in hashtable. why
not to implement it like this? i do not use selectionkey attachment bacause
of your blog :) - i agree that there are those disadvantages that you
pointed out. unneded entries from hashtable are removed whenever i close a
channel. also it is rather convenient to iterate throught connections.
-- 
View this message in context: http://www.nabble.com/-Grizzly2.0---Issue-3--Attaching-a-Connection-object-to-the-SelectionKey-tp17989586p17990263.html
Sent from the Grizzly - Development mailing list archive at Nabble.com.