[
https://issues.apache.org/jira/browse/DIRMINA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trustin Lee resolved DIRMINA-375.
---------------------------------
Resolution: Fixed
Assignee: Trustin Lee
IoSession.read() and ReadFuture have been added as discussed. To work around
the memory usage and event order problem, I added
IoSessionConfig.useReadOperation flag so user can enable or disable
IoSession.read(). Once enabled, all received messages are queued into an
internal queue.
I didn't add any timeout exception though because it can cause ambiguity as
Brad pointed out. Just calling ReadFuture.await(timeout) will return false
when the message is not received within the specified time frame.
> 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, 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.
