[ http://issues.apache.org/jira/browse/DIRMINA-92?page=comments#action_12332220 ]
Trustin Lee commented on DIRMINA-92: ------------------------------------ His implementation is very impressive and provides a lot of features, but it seems like it is designed to be very specific to a specific protocol and management environment IMHO. Here's my implementation plan: * RequestMessage which has a method 'getMessageId()' which returns an Object. The messageId type will have to implement equals and hashCode methods properly. * ResponseMessage which has a method 'getRequestMessageId()' which returns an Object. The constraint is same with that of RequestMessage. * RequestResponseProtocolFilter that remembers sent RequestMessages and fires an 'exceptionCaught' event with an appropriate 'RequestTimeoutException' to ProtocolHandler if the ResponseMessage is not arriving for certain specified time. WDYT? > Utility classes for asynchronous request-response protocols. > ------------------------------------------------------------ > > Key: DIRMINA-92 > URL: http://issues.apache.org/jira/browse/DIRMINA-92 > Project: Directory MINA > Type: New Feature > Versions: 0.7 > Reporter: Trustin Lee > Assignee: Trustin Lee > Fix For: 0.8 > Attachments: Protocol.zip > > There are so many existing asynchronous protocols whose messages have > request-response structure. A request message usually has a message ID, and > the corresponding response message, which makes a pair, contains the message > ID in the request message. > It would be great if we can provide a common interface and classes to help > users implement this type of protocols easily. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
