client side vs server side deliver pre-condition advice
I have a question about client side vs server side deliver pre-condition, that a customer asked and I want to confirm that my understanding is correct.
My customer wants to implement a control on new files being created. The work occurs in the RTC client.
1/ Is there a way now to trigger processing at check-in ? That would be the best place to do it, so that the control would be performed as early as possible.
2/ the control that the customer wants to do might be expensive in some cases. I understand that precondition running on the server side run in the context of a transaction. Delaying the commit of the transaction is not good for other transactions. In this case, is it safer to run this control as a client-side deliver pre-condition (if check-in is not available) ?
Thanks,
Nicolas
My customer wants to implement a control on new files being created. The work occurs in the RTC client.
1/ Is there a way now to trigger processing at check-in ? That would be the best place to do it, so that the control would be performed as early as possible.
2/ the control that the customer wants to do might be expensive in some cases. I understand that precondition running on the server side run in the context of a transaction. Delaying the commit of the transaction is not good for other transactions. In this case, is it safer to run this control as a client-side deliver pre-condition (if check-in is not available) ?
Thanks,
Nicolas
One answer
Hi Nicolas,
as far as I know there is no extension point for check in. I have no solution to that. You would maybe want to make sure that not more than on file goes into a change set and I think you can't. All you could do is check that at deliver.
In general you want to have server based operational behavior, rather than client side, because it is much easier to deploy and maintain (only on the server).
Client side behavior is only needed if the information it acts on is only available on the client. E.g. a syntax checking program or something like that.
I don't think you gain anything in the transaction department, since the transaction spans the client as well as the server.
as far as I know there is no extension point for check in. I have no solution to that. You would maybe want to make sure that not more than on file goes into a change set and I think you can't. All you could do is check that at deliver.
In general you want to have server based operational behavior, rather than client side, because it is much easier to deploy and maintain (only on the server).
Client side behavior is only needed if the information it acts on is only available on the client. E.g. a syntax checking program or something like that.
I don't think you gain anything in the transaction department, since the transaction spans the client as well as the server.
Comments
