[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-vcm-dev] Adding/Refreshing CVS resources programmat ically
|
>
> The client would be protected from some of the intricacies of a
> particular repository, in that an implementation of WVCM is
> responsible for interpreting the obscure error/status responses of the
> repository, and converting them into one of a standard set of
> exceptions (better that this be done once by a WVCM implementation,
> than that every client have to deal with it). This should at least
> simplify some aspects of his client.
>
> Cheers,
> Geoff
>
That would be excellent. The API should just report the exceptions to the
client and let the client decide how to deal with them (pop up an error
dialog, generate a problem marker, bring up a Synchronize view, etc.)
In my case, this would allow the client to perform a client-side auto-merge
at checkin in specified cases where we have well-defined rules for merging
and resubmit the changes to VCM without involving the user
--
Roberto Scaramuzzi
System Engineer
Parasoft, Inc.
