| Summary: | [Connection] Implement CVS redirect | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Philippe Chaléat <pch> |
| Component: | CVS | Assignee: | platform-cvs-inbox <platform-cvs-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P5 | CC: | amaguran |
| Version: | 3.1 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Philippe Chaléat
From the doc, this appears to be a server configuration that does not need special handling on the client. From the doc : "When a cvs client accesses a secondary server and only sends read requests, then the secondary server handles the entire request. If the client sends any write requests, however, the secondary server asks the client to redirect its write request to the primary server, if the client supports redirect requests, and otherwise becomes a transparent proxy for the primary server, which actually handles the write request." "(CVS 1.12.9 and earlier clients do not handle the ‘Redirect’ response)" In fact, it's not really easy to have a secondary server that acts as a "transparent proxy for the primary server". PS : The protocol is documented in doc/cvsclient.texi in the CVS source distribution. Available in servers >= 1.12.10 This is a brand new feature that it seems needs client support. We don't have plans to implement this in 3.1. but would accept a patch. There is currently no plan to address this item. As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you. |