I know what are you saying… In Documentum you use a java applet for UCF.
UCF stand for ‘Unified Content Facilities’ which is a lightweight applet that is responsible for transferring content between the content server, application server and the client machine during operations such as check-in, checkout, import etc. UCF is a Java-based client application that is installed at run-time.
What are the benifits of UCF over HTTP transfer mode and why is it being made the de-facto standard in Documentum based applications:
Performance and Throughput,Extensibility,Recovery,DFC based analysis for the client,Client information available on the server (for DFC and WDK components)…
do you know UCF????