From b704a068a92c00b50e7d5f33ef6c8e1c3a87ceae Mon Sep 17 00:00:00 2001 From: Havoc Pennington Date: Tue, 14 Oct 2003 05:22:22 +0000 Subject: - the pending reply tracking isn't quite right. It currently simply blocks any reply if one wasn't pending. Instead, it needs to allow any reply if one was pending, and block otherwise. Suggest changing the check_reply() call to just get a boolean was_pending_reply value, pass that in to the policy engine, and allow / elements to match based on whether it was a pending reply. --- doc/TODO | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/doc/TODO b/doc/TODO index c301d449..54794433 100644 --- a/doc/TODO +++ b/doc/TODO @@ -1,4 +1,4 @@ - + - How we will handle DCOP needs sorting out. Among other things, we need to check that service and service-ownership semantics map to DCOP reasonably well. @@ -118,3 +118,10 @@ - the max_replies_per_connection resource limit isn't implemented + - the pending reply tracking isn't quite right. It currently simply + blocks any reply if one wasn't pending. Instead, it needs to + allow any reply if one was pending, and block otherwise. + Suggest changing the check_reply() call to just get a boolean + was_pending_reply value, pass that in to the policy + engine, and allow / elements to match based on + whether it was a pending reply. -- cgit