|
| Script2EXE Home | How to Use | Interface | Buy | Support | Site Home |
A Pluggable Protocol can be permanent or temporary. A permanent protocol requires a separate DLL. Because Script2EXE does not want to leave garbage on your and your users' computers, it use a temporary protocol. A temporary protocol is valid only to the process that registered it. The only known problem is that some ActiveX controls, such as "SWF", does not know how to use a temporary protocol - that is, if your resource has swf files, they can not be played. If your application does not contains movie resources, you can safely select the "Temporary Pluggable Protocol" option.
When this option is selected, A HTTP server will be started inside your application to pump the data. The server works on "127.0.0.1" using a dynamic port number between 2048 and 65535.
Same as described above, but add "Expires: 10-years-ago" and "Cache-Control: no-cache" to the response header. Selec this option if you don't want your applications leave data in the Internet Cache, but remember, this option will cause the browser repeatedly request the same file each time it use it, and the result is more CPU time.