You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Trustin Lee (JIRA)" <ji...@apache.org> on 2007/11/19 01:20:43 UTC
[jira] Commented: (DIRMINA-375) Synchronous Client API
[ https://issues.apache.org/jira/browse/DIRMINA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543437 ]
Trustin Lee commented on DIRMINA-375:
-------------------------------------
I've just wrapped the exception with ExceptionHolder to fix the problem you pointed out. Thanks!
> Synchronous Client API
> ----------------------
>
> Key: DIRMINA-375
> URL: https://issues.apache.org/jira/browse/DIRMINA-375
> Project: MINA
> Issue Type: New Feature
> Reporter: Brad Harvey
> Assignee: Trustin Lee
> Fix For: 2.0.0-M1
>
> Attachments: EchoClient.java, minaClient.patch, ReadFutureTest.java, SumUpClient.java
>
>
> Hi,
> There was mention of a synchronous client api for MINA on the mailing list, so I thought I'd offer my implementation.
> http://www.nabble.com/forum/ViewPost.jtp?post=10445399&framed=y
> As far as I can tell it works, but I've never given it a good run under heavy load. The areas I think could use some review are:
> Connection - possible to use generics? Only makes sense if you can tie it to what the filters are doing I think.
> ConnectionFactoryImpl - is the managedSessions processing required?
> SequentialExecutor/DaemonThreadFactory - are there better/pre existing ways of doing these?
> Connection/NonBlockingConnection - any point having them separate? Did this initially for JCA resource adapter idea - didn't want to offer non blocking to EJB clients.
> Regards,
> Brad.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.