[
https://issues.apache.org/jira/browse/AVRO-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051177#comment-13051177
]
James Baldassari commented on AVRO-539:
---------------------------------------
Regarding the 1.5 back-port, I think it would be fine to commit it.
Is there documentation somewhere, like on the Avro website or wiki, that would
need to be updated to demonstrate the new callback functionality?
On the topic of load testing, I think it would be useful to have some sort of
utility for testing RPCs that goes beyond what the unit tests do. For example,
this test/utility would use a thread pool on the client side and would invoke
RPCs as quickly as possible against a test server. This type of test might
uncover problems like ConcurrentModificationException and other thread-safety
issues, memory leaks, and anything else that might go wrong under load. A
simple version of this test could probably be added to the existing ipc
project, perhaps bound to the integration-test phase rather than the test
phase. The default run time for the test could be short, but the test time and
number of client threads could be overridden via system properties to run a
longer test if desired. Should I create an enhancement issue for this?
> Allow asynchronous clients to specify a callback to be run when server
> processing completes
> -------------------------------------------------------------------------------------------
>
> Key: AVRO-539
> URL: https://issues.apache.org/jira/browse/AVRO-539
> Project: Avro
> Issue Type: New Feature
> Reporter: Jeff Hammerbacher
> Assignee: James Baldassari
> Fix For: 1.6.0
>
> Attachments: AVRO-539-v2-2.patch, AVRO-539-v2.patch,
> AVRO-539-v3.patch, AVRO-539-v4.patch, AVRO-539.patch
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
