 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
WinInet provides base Internet functionality for Windows Mobile devices, including support for FTP Client, Autodial, Passport, Internet Explorer 6, and the MSXML parser. The WinInet API handles all communication between the application and Windows Sockets (Winsock), freeing you from the overhead associated with establishing and maintaining the communications session. WinInet for Windows Mobile supports the HTTP and FTP Internet protocols. Windows Mobile does not support for the Gopher protocol.
Multithreaded applications can make concurrent calls to WinInet functions from different threads. WinInet functions synchronize if necessary, but do not validate parameters.
WinInet supports IPv6. For more information about IPv6, see Core Protocols of IPv6and IPv6 Addressing.
For more information about the WinInet API and Windows Internet
programming, see this
In This Section
- About HINTERNET Handles
-
Describes the hierarchy of the handles created by the WinInet functions.
- Using Asynchronous WinInet Functions
-
Provides information about using WinInet functions asynchronously.
- Platform for Privacy Preferences (P3P)
-
Provides information about how you can add cookie handling in your applications.
- Caching
-
Provides information about how to use built-in caching in WinInet applications.
- HTTP and FTP Common Functions
-
Provides reference information about the functions that are used in HTTP and FTP related tasks.
- HTTP Sessions
-
Provides information about how you can use WinInet functions to handle the HTTP protocol to access resources on the World Wide Web.
- FTP Sessions
-
Describes the WinInet functions that enable applications to navigate and manipulate directories and files on an FTP server.
Related Sections
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.