added a JIRA entry. Number 317, and also added a patch to support creation time. Will start working on the others...
On 11/27/06, Mark Webb <[EMAIL PROTECTED]> wrote:
That is what I was thinking. the concurrent.atomic package is your friend :) On 11/27/06, Gaston Dombiak <[EMAIL PROTECTED]> wrote: > Hey Guys, > > I'm 100% new to MINA but if you are using Java 1.5 as a prerequisite > then you can try using AtomicLong or one of its sibling to reduce > performance impact and at the same time ensure a thread safe solution. > > -- Gato > > -----Original Message----- > From: Trustin Lee [mailto:[EMAIL PROTECTED] > Sent: Monday, November 27, 2006 4:53 PM > To: dev@mina.apache.org > Subject: Re: IoService question > > On 11/27/06, Mark Webb <[EMAIL PROTECTED]> wrote: > > > > I was looking at the IoService class and noticed that there are some > > fields > > that would be nice to have: > > > > long getCreationTime(); > > long getReadBytes(); > > long getWrittenBytes(); > > long getReadMessages(); > > long getWrittenMessages(); > > > > These methods are in the IoSession interface, and thought it would > make > > sense to also have them in the IoService interface. The last 4 might > be a > > little tougher to implement, but it would be nice for times in which > we > > need > > some performance numbers. > > > > comments/questions? > > > Sounds like a good idea. But wouldn't we need any synchronization which > might degrade performance? We could just skip synchronization if we > just > want approximate numbers. > > Trustin > -- > what we call human nature is actually human habit > -- > http://gleamynode.net/ > -- > PGP key fingerprints: > * E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E > * B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6 >
