[RIVER-104] (mux) in Abort messages sent from server, use "partial" flag more intelligently

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: jtsk_2.0
• Component/s: net_jini_jeri
• Bugtraq ID: 5037395
• Assignee: Unassigned
• Reporter: Thomas Vinod Johnson
• Created: 27/Jul/07 14:40
• Updated: 27/Jul/07 14:40

Description

5037395
In the current implementation, when an Abort message is sent from the server side of a connection, the "partial" flag is always set, indicating that request data sent by the client may have been processed (with possible side effects) on the server side. The current behavior is unnecessarily conservative; the implementation should leave the "partial" flag unset in situations in which it can guarantee that client retry is safe.

It seems that one such situation is when ServerConnection.processRequestData throws an exception-- in that case, we can guarantee to the client that the RequestDispatcher (above the current connection-oriented transport provider) has not been invoked for the request, and that is what OutboundRequest.getDeliveryStatus is specified with respect to.

Evaluation: The particular case described here would seem to be more cleanly implementable after River-103 has been addressed