mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julien Vermillard <jvermill...@archean.fr>
Subject Re: svn commit: r565676 - in /mina/trunk: core/src/main/java/org/apache/mina/common/ core/src/main/java/org/apache/mina/transport/socket/nio/ core/src/main/java/org/apache/mina/transport/socket/nio/support/ core/src/main/java/org/apache/mina/transpor
Date Mon, 20 Aug 2007 15:29:12 GMT
On Mon, 20 Aug 2007 23:42:37 +0900
"Trustin Lee" <trustin@gmail.com> wrote:

> On 8/20/07, peter royal <proyal@apache.org> wrote:
> > On Aug 14, 2007, at 2:40 AM, trustin@apache.org wrote:
> > > Renamed TransportType to IoServiceMetadata because it stands what
> > > it does more precisely
> >
> > This name seems odd to me.. I think of a 'service' as what I'm
> > providing.. and MINA makes my service available over various
> > transports (TCP,UDP,in-VM, etc)
> >
> > I do agree about it being 'Metadata' vs 'Type' though.
> >
> > How about TransportMetadata?

Sound good for me too
> 
> TransportMetadata sounds good.  Then should we rename
> IoService.getMetadata() to getTransportMetadata()?  We could also
Yes, will be more understandable.
> resurrect IoSession.getTransportMetadata() (was: getTransportType()).

I liked this API change, since it's quite redundant.

Julien

Mime
View raw message