Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 351160 - Automatically send client-side protocol timeouts to server, as well
Summary: Automatically send client-side protocol timeouts to server, as well
Status: CLOSED FIXED
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.net4j (show other bugs)
Version: 4.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Eike Stepper CLA
QA Contact: Eike Stepper CLA
URL:
Whiteboard: Lighter, Faster and Better
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-05 06:14 EDT by Eike Stepper CLA
Modified: 2012-09-21 07:16 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eike Stepper CLA 2011-07-05 06:14:16 EDT 
When a client calls ISignalProtocol.setTimeout(x) then x should also be set as the timeout value on the server-side peer of that protocol.
Comment 1 Eike Stepper CLA 2011-07-05 06:16:55 EDT 
Note that it has always been possible to explicitely set the server-side timeout, as outlined in bug 350146 comment 5.

This bugzilla is about making that happen automatically so that client and server side timeouts are always in sync.
Comment 2 Eike Stepper CLA 2011-07-05 06:18:37 EDT 
Committed revision 8596

Note that this new behaviour is on by default and can be changed by overriding SignalProtocol.isSendingTimeoutChanges().
Comment 3 Eike Stepper CLA 2012-09-21 07:16:06 EDT 
Closing.