commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rory Winston (JIRA)" <>
Subject [jira] Resolved: (NET-127) [net] Reminder/Request for using nio instead of Threads
Date Sat, 26 Aug 2006 16:41:23 GMT
     [ ]

Rory Winston resolved NET-127.

    Resolution: Later

> [net] Reminder/Request for using nio instead of Threads
> -------------------------------------------------------
>                 Key: NET-127
>                 URL:
>             Project: Commons Net
>          Issue Type: Improvement
>         Environment: Operating System: All
> Platform: All
>            Reporter: Jeroen Cranendonk
>            Priority: Minor
> I saw in the archives this has sometimes come up already, this is just a vote
> and a persistent reminder to it :)
> My case:
> Currently commons-net uses Threads for everything, aka every socket has it's own
> Thread.
> With the j2se1.4 nio package it's possibly to use selectors and unblocking
> sockets instead of using threads.
> This is often a better approach, and should to my opinion be either optional or
> default in commons net.
> My specific reason/example for this is that when building a talker/mud (multi
> user telnet text chat/game environment) having a Thread for each socket
> increases the complexity tremendiously compared to a single thread in
> combination with a nio selector. While there is no good reason to actulaly use
> threads, a talker needs no great performance or simultanous processing of
> incoming messages.
> For now I'm left building my own only half decent nio telnet classes ;)
> I'd much rather use commons :)
> Keep up the good work! :)
>    Jeroen Cranendonk

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message