[ https://issues.apache.org/jira/browse/DIRMINA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532763
]
Mike Heath commented on DIRMINA-375:
------------------------------------
+1
I really like the idea of having an IoSession.read() method that returns a ReadFuture so that
you can block and/or register a IoFutureListener that handles the next message received.
This would greatly simplify so much of the state management we currently have to do in our
IoHandler's.
Let me know where I can help with integrating this into trunk.
> Synchronous Client API
> ----------------------
>
> Key: DIRMINA-375
> URL: https://issues.apache.org/jira/browse/DIRMINA-375
> Project: MINA
> Issue Type: New Feature
> Reporter: Brad Harvey
> 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.
|