Consultor Eletrônico

Status: Verified

GOAL:

How does the WSASP messenger work with Progress, OpenEdge Releases?

GOAL:

How is the WSASP messenger designed to work with Progress 9.1D and prior?

GOAL:

How is the WSASP messenger designed to work with Progress 9.1E?

GOAL:

How is the WSASP messenger designed to work with OpenEdge Release?

GOAL:

What DLLs are used with WSASP messenger?

FACT(s) (Environment):

WebSpeed 3.1x
Progress 9.1x
OpenEdge 10.x
Windows NT 32 Intel/Windows 2000

FIX:

The Progress ASP Messenger (WSASP) runs inside the IIS Service.
With Progress Version 9.1D/3.1D and Prior Versions of 9.1x/3.1x Family:
In WebSpeed 3.1D or prior, the WebSpeed WSASP Messenger used the Windows client DLL WinInet.dll in order to obtain some of its functionality. WinInet.dll is designed for use with a client application (such as Internet Explorer), and was not designed for use in a service. Consequently, in 9.1D and prior versions of 3.1x, it was possible to get poor performance and/or system crashes when using the WSASP messenger.

With OpenEdge Release 10.0A and Higher:
From OpenEdge Release 10.0A, the WSASP messenger uses WinHTTP.dll instead of WinInet.dll. WinHTTP.dll is designed for use in services. All certified OpenEdge 10.0A Windows platforms provide WinHTTP.dll by default, so it will always be available.

With Progress Version 9.1E/3.1E:
For the 9.1E WSASP messenger, it is not possible to use WinHTTP.dll all the time, as 9.1E has to run on Windows NT 4.0 server. Microsoft does not supply WinHTTP.dll for Windows NT 4.0. There is an older alternative to WinHTTP.dll, called winHTTP5.dll, which is not guaranteed to be on a user's Windows NT 4.0 system.

For these reasons, the 9.1E WSASP Messenger changes the way it loads the required DLL. In 9.1E, the WSASP Messenger dynamically looks for an available DLL to provide the necessary functionality, in the following
order:

- winhttp.dll
- winhttp5.dll
- wininet.dll