NOTICE: Our Community is moving. Get more information.
Silk Performer is capable of recording a broad range of application types and technologies. To do so, Silk Performer uses various recording methods, which can be confusing at times. To make things a bit more clear, we're going to outline the theory of how recording in Silk Performer works.
Take a look at the diagram below. Silk Performer uses four recording methods, which can be categorized into two basic recording approaches: (1) The hooking approach and (2) the proxy approach. The hooking approach uses the SOCKS protocol and port 19120. It can be used to record either only the new instances of a browser, or all new and running instances. The proxy approach uses the HTT protocol and port 8080. It can either make use of the system proxy or the application proxy.
The following diagram shows the principles of the application proxy method. Basically, the client - in this case a web browser - is configured to connect to the server through the Recorder. Thus the Recorder acts as a proxy. If the browser does so using its own proxy settings, we're refering to this as the application proxy method.
If the browser connects to the server using the generic proxy settings of the Windows operating system, we're talking about the system proxy method. This method can cause side effects, since a number of other applications might also use the generic system proxy settings.
To learn how to actually set a specific recording method within Silk Performer, watch the following video. Also, you can find this information in the Silk Performer Help: Recording Methods for Recording Profiles
To learn more about all new features and enhancements Silk Performer 19.0 provides, take a look at the following blog posts:
The Silk Performer Help is another comprehensive source of information.
If this article was useful for you, leave us a comment or like it. We appreciate your feedback.